From: Alex Markuze <alex-I7wstvAgZDk@public.gmane.org>
To: sothy shan <sothy.e98-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Intel DPDK: exception_path:RTE_ARCH
Date: Wed, 2 Jul 2014 12:56:07 +0300 [thread overview]
Message-ID: <CAKfHP0XNmn4zCPd2+42gCLKJw_AS1qonMPiHtLX4ghHBUDR76w@mail.gmail.com> (raw)
In-Reply-To: <CAHcF_0YYXi8KiVReuZW7YTWLLDL0A7Ui1fb4qTJpo0C7JoPqRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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
On Wed, Jul 2, 2014 at 12:48 PM, sothy shan <sothy.e98-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello!
>
> 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?
>
> Thanks for your reponse.
>
> Best regards
> Sothy
>
next prev parent reply other threads:[~2014-07-02 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:48 Intel DPDK: exception_path:RTE_ARCH sothy shan
[not found] ` <CAHcF_0YYXi8KiVReuZW7YTWLLDL0A7Ui1fb4qTJpo0C7JoPqRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 9:56 ` Alex Markuze [this message]
[not found] ` <CAKfHP0XNmn4zCPd2+42gCLKJw_AS1qonMPiHtLX4ghHBUDR76w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 10:00 ` Thomas Monjalon
2014-07-02 10:04 ` sothy shan
[not found] ` <CAHcF_0aWq+EvJechqM9bhVWLFZ9bcSpDt=YG_xNQLYHG-ejWNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 14:19 ` sothy shan
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=CAKfHP0XNmn4zCPd2+42gCLKJw_AS1qonMPiHtLX4ghHBUDR76w@mail.gmail.com \
--to=alex-i7wstvagzdk@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=sothy.e98-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).