From: Vasiliy Tolstov <v.tolstov@selfip.ru>
To: dev <dev@dpdk.org>
Subject: [dpdk-dev] failed to build latest dpdk 1.8.0 on kvm virtual machine
Date: Wed, 11 Mar 2015 16:47:28 +0300 [thread overview]
Message-ID: <CACaajQui7Oev=ZyTuzckovUSPsnAc0Fx+dmEHNe1v1MoO_RfaA@mail.gmail.com> (raw)
I'm try to build dpdk 1.8.0
unpack sources
sed -i 's|CONFIG_RTE_MACHINE="native"|CONFIG_RTE_MACHINE="default"|g'
config/defconfig_x86_64-native-linuxapp-gcc
export CFLAGS="-march=core2 -mtune=generic -pipe -O2"
make V=1 config T=x86_64-native-linuxapp-gcc
make V=1 MACHINE_CFLAGS="${CFLAGS}"
/var/tmp/paludis/build/net-dpdk-1.8.0/work/dpdk-1.8.0/mk/internal/rte.compile-pre.mk:126:
recipe for target 'eal_common_cpuflags.o' failed
/var/tmp/paludis/build/net-dpdk-1.8.0/work/dpdk-1.8.0/lib/librte_eal/common/eal_common_cpuflags.c:
In function 'rte_cpu_check_supported':
/var/tmp/paludis/build/net-dpdk-1.8.0/work/dpdk-1.8.0/lib/librte_eal/common/eal_common_cpuflags.c:63:4:
error: 'RTE_COMPILE_TIME_CPUFLAGS' undeclared (first use in this
function)
RTE_COMPILE_TIME_CPUFLAGS
^
--
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru
next reply other threads:[~2015-03-11 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 13:47 Vasiliy Tolstov [this message]
2015-03-11 14:14 ` Mcnamara, John
2015-03-11 15:25 ` Vasiliy Tolstov
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='CACaajQui7Oev=ZyTuzckovUSPsnAc0Fx+dmEHNe1v1MoO_RfaA@mail.gmail.com' \
--to=v.tolstov@selfip.ru \
--cc=dev@dpdk.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).