From: Marco Varlese <mvarlese@suse.de>
To: dev@dpdk.org
Subject: [dpdk-dev] Issue building for ppc64le
Date: Tue, 27 Feb 2018 17:08:36 +0100 [thread overview]
Message-ID: <1519747716.3553.15.camel@suse.de> (raw)
Hi,
Is anybody else experiencing issues with building DPDK 17.11 for ppc64le?
Any help would be very much appreciated.
I get the below error:
== START ==
[ 326s] gcc -Wp,-MD,./.power_manager.o.d.tmp -m64 -pthread -fPIC -
DRTE_MACHINE_CPUFLAG_PPC64 -DRTE_MACHINE_CPUFLAG_ALTIVEC
-DRTE_MACHINE_CPUFLAG_VSX -I/home/abuild/rpmbuild/BUILD/dpdk-17.11/ppc_64-
power8-linuxapp-gcc/examples/vm_power_manager/ppc_64-power8-linuxapp-gcc/include
-I/home/abuild/rpmbuild/BUILD/dpdk-17.11/ppc_64-power8-linuxapp-gcc/include
-include /home/abuild/rpmbuild/BUILD/dpdk-17.11/ppc_64-power8-linuxapp-
gcc/include/rte_config.h -O3 -I/home/abuild/rpmbuild/BUILD/dpdk-
17.11/lib/librte_power/ -W -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations -Wold-style-definition -Wpointer-arith -Wcast-align
-Wnested-externs -Wcast-qual -Wformat-nonliteral -Wformat-security -Wundef
-Wwrite-strings -Wimplicit-fallthrough=2 -Wno-format-truncation -
DVERSION="17.11" -o power_manager.o -c /home/abuild/rpmbuild/BUILD/dpdk-
17.11/examples/vm_power_manager/power_manager.c
[ 327s] /home/abuild/rpmbuild/BUILD/dpdk-
17.11/examples/vm_power_manager/main.c:61:10: fatal error: rte_pmd_ixgbe.h: No
such file or directory
[ 327s] #include <rte_pmd_ixgbe.h>
[ 327s] ^~~~~~~~~~~~~~~~~
[ 327s] compilation terminated.
[ 327s] make[4]: *** [/home/abuild/rpmbuild/BUILD/dpdk-
17.11/mk/internal/rte.compile-pre.mk:140: main.o] Error 1
[ 327s] make[4]: *** Waiting for unfinished jobs....
== END ==
Cheers,
--
Marco V
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
next reply other threads:[~2018-02-27 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 16:08 Marco Varlese [this message]
2018-02-27 18:15 ` Ferruh Yigit
2018-02-28 6:47 ` Marco Varlese
2018-02-28 7:01 ` Marco Varlese
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=1519747716.3553.15.camel@suse.de \
--to=mvarlese@suse.de \
--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).