From: "Keith E. Fleming" <kef762@yahoo.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK 2.1.0 build error: inlining failed in call to always_inline
Date: Thu, 20 Aug 2015 17:35:10 +0000 (UTC) [thread overview]
Message-ID: <2084044903.8110244.1440092110627.JavaMail.yahoo@mail.yahoo.com> (raw)
make config T=x86_64-native-linuxapp-gccsed -ri 's,(PMD_PCAP=).*,\1y,' build/.configmake
[root@neutron dpdk-2.1.0]# make 2>&1 | more
== Build lib
== Build lib/librte_compat
== Build lib/librte_eal
== Build lib/librte_eal/common
== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/igb_uio
(cat /dev/null; echo kernel//root/dpdk-2.1.0/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko;) > /root/dpdk-2.1.0/build/build
/lib/librte_eal/linuxapp/igb_uio/modules.order
Building modules, stage 2.
MODPOST 1 modules
== Build lib/librte_eal/linuxapp/eal
CC eal_common_options.o
In file included from /usr/lib/gcc/x86_64-redhat-linux/4.9.2/include/x86intrin.h:37:0,
from /root/dpdk-2.1.0/build/include/rte_vect.h:67,
from /root/dpdk-2.1.0/build/include/rte_memcpy.h:46,
from /root/dpdk-2.1.0/lib/librte_eal/common/eal_common_options.c:48:
/root/dpdk-2.1.0/build/include/rte_memcpy.h: In function ‘rte_memcpy’:
/usr/lib/gcc/x86_64-redhat-linux/4.9.2/include/tmmintrin.h:185:1: error: inlining failed in call to always_inline ‘_mm_alignr_epi8’: t
arget specific option mismatch
_mm_alignr_epi8(__m128i __X, __m128i __Y, const int __N)
^
In file included from /root/dpdk-2.1.0/lib/librte_eal/common/eal_common_options.c:48:0:
/root/dpdk-2.1.0/build/include/rte_memcpy.h:425:9: error: called from here
I can't even guess at what the problem is here. It's a total trainwreck. I assume this has compiled successfully for someone somewhere? Thanks
next reply other threads:[~2015-08-20 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 17:35 Keith E. Fleming [this message]
2015-08-21 10:54 ` Bruce Richardson
2015-08-21 15:13 ` Keith E. Fleming
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=2084044903.8110244.1440092110627.JavaMail.yahoo@mail.yahoo.com \
--to=kef762@yahoo.com \
--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).