From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: Ashwini Thaokar <thaokar.a@husky.neu.edu>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK installation
Date: Mon, 27 Mar 2017 07:58:37 +0200 [thread overview]
Message-ID: <CAATJJ0+Tp3vjRO96zfnsmGZb-YF2gSrJZqnVFFmKrBkTkJx0MQ@mail.gmail.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897476FFEDF@IRSMSX108.ger.corp.intel.com>
On Fri, Mar 24, 2017 at 8:22 PM, De Lara Guarch, Pablo <
pablo.de.lara.guarch@intel.com> wrote:
> Looks like you don't have icc installed.
> Use the x86_64-native-linuxapp-gcc instead:
>
> make install T=x86_64-native-linuxapp-gcc
>
Ack to that,
and since there are more dependencies you might want to satisfy to can at
least get close very easily.
Since DPDK is in Ubuntu you can with one line get what we use to build it.
$ sudo apt-get build-dep dpdk
I say only "close" since this is what we used to build the version in the
respective release, e.g. dpdk 2.2 in xenial.
And also extra deps can depend on your config still.
P.S. ok, maybe a few more lines if you have not yet uncommented the deb-src
lines in /etc/apt/sources.list, but "apt-get build-dep" will tell you so if
needed.
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2017-03-27 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 19:13 Ashwini Thaokar
2017-03-24 19:22 ` De Lara Guarch, Pablo
2017-03-27 5:58 ` Christian Ehrhardt [this message]
2017-03-29 19:43 [dpdk-dev] DPDK Installation Ashwini Thaokar
2017-03-30 5:58 ` Christian Ehrhardt
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=CAATJJ0+Tp3vjRO96zfnsmGZb-YF2gSrJZqnVFFmKrBkTkJx0MQ@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thaokar.a@husky.neu.edu \
/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).