From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shreyansh.jain@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw19724 [PATCH v10 13/13] doc: remove deprecation notice for rte_bus
Date: 18 Jan 2017 10:07:00 -0800 [thread overview]
Message-ID: <5727c7$up5e9@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7209 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/19724
_Compilation issues_
Submitter: Shreyansh Jain <shreyansh.jain@nxp.com>
Date: Wed, 18 Jan 2017 19:35:19 +0530
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:b1cbca1e7f4d2fd2a3323f636f53faabcb89f79c
Patch19712-19724 --> compile error
Build Summary: 18 Builds Done, 16 Successful, 2 Failures
Test environment and configuration as below:
OS: RHEL7.2_64
Kernel Version:3.10.0-327.el7.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version:3.4.2
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
OS: FreeBSD10.3_64
Kernel Version:10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
Clang Version:3.4.1
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
OS: FC24_64
Kernel Version:4.8.6-201.fc24.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Clang Version:3.8.0
x86_64-native-linuxapp-clang
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc-debug
OS: UB1604_64
Kernel Version:4.4.0-53-generic
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Clang Version:3.8.0
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: CentOS7_64
Kernel Version:3.10.0-327.el7.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version:3.4.2
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
Failed Build #1:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-clang
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:317:22: error: use of undeclared identifier 'pci_device_list'
TAILQ_INSERT_TAIL(&pci_device_list, dev, next);
^
/usr/include/sys/queue.h:703:27: note: expanded from macro 'TAILQ_INSERT_TAIL'
(elm)->field.tqe_prev = (head)->tqh_last; \
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:317:22: error: use of undeclared identifier 'pci_device_list'
/usr/include/sys/queue.h:704:4: note: expanded from macro 'TAILQ_INSERT_TAIL'
*(head)->tqh_last = (elm); \
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:317:22: error: use of undeclared identifier 'pci_device_list'
/usr/include/sys/queue.h:705:3: note: expanded from macro 'TAILQ_INSERT_TAIL'
(head)->tqh_last = &TAILQ_NEXT((elm), field); \
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:323:24: error: use of undeclared identifier 'pci_device_list'
TAILQ_FOREACH(dev2, &pci_device_list, next) {
^
/usr/include/sys/queue.h:617:28: note: expanded from macro 'TAILQ_FOREACH'
for ((var) = TAILQ_FIRST((head)); \
^
/usr/include/sys/queue.h:614:29: note: expanded from macro 'TAILQ_FIRST'
#define TAILQ_FIRST(head) ((head)->tqh_first)
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:340:22: error: use of undeclared identifier 'pci_device_list'
TAILQ_INSERT_TAIL(&pci_device_list, dev, next);
^
/usr/include/sys/queue.h:703:27: note: expanded from macro 'TAILQ_INSERT_TAIL'
(elm)->field.tqe_prev = (head)->tqh_last; \
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:340:22: error: use of undeclared identifier 'pci_device_list'
/usr/include/sys/queue.h:704:4: note: expanded from macro 'TAILQ_INSERT_TAIL'
*(head)->tqh_last = (elm); \
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:340:22: error: use of undeclared identifier 'pci_device_list'
/usr/include/sys/queue.h:705:3: note: expanded from macro 'TAILQ_INSERT_TAIL'
(head)->tqh_last = &TAILQ_NEXT((elm), field); \
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:668:1: warning: no previous prototype for function 'rte_eal_pci_init' [-Wmissing-prototypes]
rte_eal_pci_init(void)
^
1 warning and 8 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'eal_pci.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'eal' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'bsdapp' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_eal' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:126: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:101: recipe for target 'install' failed
Failed Build #2:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
In file included from /home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:48:0:
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c: In function 'pci_scan_one':
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:316:19: error: 'pci_device_list' undeclared (first use in this function)
if (TAILQ_EMPTY(&pci_device_list)) {
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:316:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c: At top level:
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_pci.c:668:1: warning: no previous prototype for 'rte_eal_pci_init' [-Wmissing-prototypes]
rte_eal_pci_init(void)
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'eal_pci.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'eal' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'bsdapp' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_eal' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:78: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:126: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:101: recipe for target 'install' failed
DPDK STV team
reply other threads:[~2017-01-18 18:07 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='5727c7$up5e9@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=shreyansh.jain@nxp.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).