From: sothy shan <sothy.e98@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Intel DPDK: exception_path:RTE_ARCH
Date: Wed, 2 Jul 2014 16:19:15 +0200 [thread overview]
Message-ID: <CAHcF_0a9yXvDqBTv1EM7Hs78w-uwdoT1qTJwfo5TeLnGBvTSVA@mail.gmail.com> (raw)
In-Reply-To: <CAHcF_0aWq+EvJechqM9bhVWLFZ9bcSpDt=YG_xNQLYHG-ejWNQ@mail.gmail.com>
On Wed, Jul 2, 2014 at 12:04 PM, sothy shan <sothy.e98@gmail.com> wrote:
>
>
>
> On Wed, Jul 2, 2014 at 12:00 PM, Thomas Monjalon <
> thomas.monjalon@6wind.com> wrote:
>
>> 2014-07-02 12:56, Alex Markuze:
>> > On Wed, Jul 2, 2014 at 12:48 PM, sothy shan <sothy.e98@gmail.com>
>> wrote:
>> > > I started playing Intel DPDK example. I used to compile exception_path
>> > > code.
>> > > When I do make command "make", I got an error,
>> > >
>> > > RTE_ARCH is not set. So I set the variable via terminal bash using
>> > >
>> > > export RTE_ARCH=x86_64
>> > >
>> > > Stilll it is not working. Any wrong anywhere?
>> >
>> > You need, to define the following variables before compiling, please
>> refer
>> > to the DPDK documentation.
>> >
>> > export RTE_TARGET=x86_64-native-linuxapp-gcc
>> >
>> > export RTE_SDK=/home/user/dpdk
>>
>> You can also try to build all examples with these commands:
>> RTE_TARGET=x86_64-native-linuxapp-gcc
>> make T=$RTE_TARGET install
>> make T=$RTE_TARGET examples O=$RTE_TARGET/examples
>>
>> (with DPDK >= 1.7)
>>
>>
>
> When using DPDK 1.7, example/exception_path works. now playing with it. thx
next prev parent reply other threads:[~2014-07-02 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:48 sothy shan
2014-07-02 9:56 ` Alex Markuze
2014-07-02 10:00 ` Thomas Monjalon
2014-07-02 10:04 ` sothy shan
2014-07-02 14:19 ` sothy shan [this message]
2014-07-02 12:24 ` 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_0a9yXvDqBTv1EM7Hs78w-uwdoT1qTJwfo5TeLnGBvTSVA@mail.gmail.com \
--to=sothy.e98@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@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).