From: sys_stv@intel.com
To: krytarowski@caviumnetworks.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw10186-10187 tools: Add support for handling built-in kernel modules
Date: 04 Feb 2016 23:56:54 -0800 [thread overview]
Message-ID: <acb6cf$r2u1pt@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: Compile error
Patchwork ID: 10186-10187
http://www.dpdk.org/dev/patchwork/patch/10187/
Submitter: Kamil Rytarowski <krytarowski@caviumnetworks.com>
Date: Thu, 28 Jan 2016 14:13:53 +0100
DPDK git baseline: c344eab3eecb71203681e6c5c5b64aefb2d7ad94
x86_64-native-linuxapp-gcc:
Configuration done^M
== Build lib^M
== Build lib/librte_compat^M
== Build lib/librte_eal^M
== Build lib/librte_eal/common^M
== Build lib/librte_eal/linuxapp^M
== Build lib/librte_eal/linuxapp/igb_uio^M
(cat /dev/null; echo kernel//root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko;) > /root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/modules.order^M
Building modules, stage 2.^M
MODPOST 1 modules^M
== Build lib/librte_eal/linuxapp/eal^M
CC eal.o^M
/root/dpdk/lib/librte_eal/linuxapp/eal/eal.c: In function rte_eal_check_module:
/root/dpdk/lib/librte_eal/linuxapp/eal/eal.c:912:2: error: implicit declaration of function stat [-Werror=implicit-function-dd
eclaration]^M
if (stat("/sys/module", &st) != 0) {^M
^^M
/root/dpdk/lib/librte_eal/linuxapp/eal/eal.c:912:2: error: nested extern declaration of stat [-Werror=nested-externs]^M
cc1: all warnings being treated as errors^M
make[7]: *** [eal.o] Error 1^M
make[6]: *** [eal] Error 2^M
make[5]: *** [linuxapp] Error 2^M
make[4]: *** [librte_eal] Error 2^M
make[3]: *** [lib] Error 2^M
make[2]: *** [all] Error 2^M
make[1]: *** [pre_install] Error 2^M
make: *** [install] Error 2
DPDK STV team
reply other threads:[~2016-02-05 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='acb6cf$r2u1pt@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=krytarowski@caviumnetworks.com \
--cc=test-report@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).