From: sothy shan <sothy.e98@gmail.com>
To: Olivier MATZ <olivier.matz@6wind.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:07:46 +0100 [thread overview]
Message-ID: <CAHcF_0aNiDksGEU3hofHYai2ddYyLKdHaNKc-y_t3Uns4uoJ4g@mail.gmail.com> (raw)
In-Reply-To: <54B91FE3.8010607@6wind.com>
On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ <olivier.matz@6wind.com> wrote:
> Hi Sothy,
>
> On 01/16/2015 03:10 PM, sothy shan wrote:
>> I guess you are completely wrong.
>>
>> Becasue when I do
>>
>> make config T=x86_64-ivshmem-linuxapp-gcc
>> make
>>
>> Testpmd works.
>>
>> 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
>
> As far as I know, RTE_SDK and RTE_TARGET must be defined when building
> an external application (like in examples), not when building test-pmd
> app which is a sdk built-in.
If I understand the your idea, I should compile and run DPDK OVS
directly rather than DPDK testpmd. Isnt it? I will try now this.
Before, I tries testpmd and then go for DPDK OVS.
>
> Also, I'm not sure passing a CONFIG_XYZ=y variable will be properly
> taken in account by the build system. Where did you found this syntax?
https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md
> The proper way is:
>
> make config T=x86_64-ivshmem-linuxapp-gcc O=my_dir
> ${EDITOR} my_dir/.config
> make O=my_dir
>
> One last comment, please be careful when copy/pasting commands in
> mails as there are typos in some of your commands. A reader could
> expect that your problem comes from this:
>
> $ export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> $ echo $RTE_SDK
> /home/userexport
>
Sorry for mistake and I will do with care nw.
> Regards,
> Olivier
next prev parent reply other threads:[~2015-01-16 16:07 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 [this message]
2015-01-16 16:35 ` Olivier MATZ
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=CAHcF_0aNiDksGEU3hofHYai2ddYyLKdHaNKc-y_t3Uns4uoJ4g@mail.gmail.com \
--to=sothy.e98@gmail.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).