From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: liang.j.ma@intel.com
Subject: [dpdk-test-report] |FAILURE| pw32313 [PATCH v2 7/8] event/opdl: update the build system to enable compilation
Date: 26 Dec 2017 00:57:24 -0800 [thread overview]
Message-ID: <1f4ae4$kdag4@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 9449 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32313
_Compilation issues_
Submitter: liang.j.ma@intel.com
Date: Fri, 15 Dec 2017 11:26:23 +0000
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:91a0eabf00cbd78a8630ff1b9279af1b2db92122
Patch32307-32313 --> compile error
Build Summary: 16 Builds Done, 11 Successful, 5 Failures
Test environment and configuration as below:
OS: RHEL7.3_64
Kernel Version:3.10.0-514.16.1.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-11)
Clang Version:NA
x86_64-native-linuxapp-icc
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.9.13-100.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-78-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-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
OS: CentOS7_64
Kernel Version:3.10.0-514.10.2.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: RHEL7.3_64
Target: x86_64-native-linuxapp-icc
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(287): error: type name is not allowed
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(287): error: expected a ";"
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(287): error: identifier "i" is undefined
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(397): error: type name is not allowed
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(397): error: expected a ";"
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(397): error: identifier "i" is undefined
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(406): error: type name is not allowed
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c(406): error: expected a ";"
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
compilation aborted for /home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c (code 2)
Failed Build #2:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function 'opdl_queue_setup':
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: error: 'for' loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function 'opdl_dump':
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:2: error: 'for' loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:16: error: redefinition of 'i'
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:16: note: previous definition of 'i' was here
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:2: error: 'for' loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'opdl_evdev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'opdl' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'event' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:76: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:128: 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:107: recipe for target 'install' failed
Failed Build #3:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function ‘opdl_queue_setup’:
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function ‘opdl_dump’:
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:16: error: redefinition of ‘i’
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:16: note: previous definition of ‘i’ was here
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
Failed Build #4:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function ‘opdl_queue_setup’:
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function ‘opdl_dump’:
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:16: error: redefinition of ‘i’
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:16: note: previous definition of ‘i’ was here
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
Failed Build #5:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function ‘opdl_queue_setup’:
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_q_md; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:287:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c: In function ‘opdl_dump’:
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:16: error: redefinition of ‘i’
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:397:16: note: previous definition of ‘i’ was here
for (uint32_t i = 0; i < device->nb_opdls; i++)
^
/home/patchWorkOrg/compilation/drivers/event/opdl/opdl_evdev.c:406:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (uint32_t i = 0; i < device->max_port_nb; i++) {
^
DPDK STV team
reply other threads:[~2017-12-26 8:57 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='1f4ae4$kdag4@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=liang.j.ma@intel.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).