DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz@6wind.com>
To: sothy shan <sothy.e98@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
Date: Fri, 16 Jan 2015 17:35:26 +0100	[thread overview]
Message-ID: <54B93DCE.50607@6wind.com> (raw)
In-Reply-To: <CAHcF_0aNiDksGEU3hofHYai2ddYyLKdHaNKc-y_t3Uns4uoJ4g@mail.gmail.com>

Hi Sothy,

On 01/16/2015 05:07 PM, sothy shan wrote:
> On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ <olivier.matz@6wind.com> wrote:
>>> When I do  with
>>>
>>> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
>>> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
>>> install T="$RTE_TARGET"
>>
>> Are you sure that this syntax is supported by the build system?
> 
> I am tryiting to build DPDK OVS and found  the instruction in
> https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md

I just noticed the syntax is strange, you can check the supported
options here:

http://dpdk.org/doc/guides/prog_guide/dev_kit_build_system.html#makefile-description

I'm not sure the CONFIG_ will be taken in account when generating
rte_config.h (see rte.sdkconfig.mk and scripts/gen-config-h.sh). But
maybe it's not related to your issue.

Regards,
Olivier

  reply	other threads:[~2015-01-16 16:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 13:26 sothy shan
2014-12-24 15:03 ` Masaru Oki
2014-12-24 15:04 ` Neil Horman
2014-12-25  9:11   ` sothy shan
2014-12-25 17:08     ` Neil Horman
2014-12-26  8:01       ` sothy shan
2014-12-26 14:37         ` Neil Horman
2015-01-09 16:20           ` sothy shan
2015-01-10 12:44             ` Neil Horman
2015-01-16 14:10               ` sothy shan
2015-01-16 14:27                 ` Olivier MATZ
2015-01-16 16:07                   ` sothy shan
2015-01-16 16:35                     ` Olivier MATZ [this message]
2015-01-16 16:47                       ` sothy shan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B93DCE.50607@6wind.com \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=sothy.e98@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).