From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw47245[v1, 2/9] app/procinfo: add compare for new options
Date: 23 Oct 2018 07:12:13 -0700 [thread overview]
Message-ID: <0590c7$316e56@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5156 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/47245
_Compilation issues_
Submitter: Vipin Varghese <vipin.varghese@intel.com>
Date: 2018-10-23 13:57:44
DPDK git baseline: Repo:dpdk-master, CommitID: 198b66b9461c01558d4fb474d1485d1312bf2650
Build Summary: 15 Builds Done, 12 Successful, 3 Failures
Test environment and configuration as below:
OS: FC25
Kernel Version: 4.5.5-300.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.1.1 20160510 (Red Hat 6.1.1-2)
Clang Version: 3.8.0 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-debug
OS: FC24
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 (tags/RELEASE_380/final)
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: CENTOS
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 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-clang
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
OS: UB1604
Kernel Version: 4.4.0-137-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: FreeBSD
Kernel Version: 10.3-RELEASE
CPU info: cat: /proc/cpuinfo: No such file or directory
GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
*Failed Build #1:
OS: CENTOS
Target: i686-native-linuxapp-gcc
INSTALL-LIB librte_pmd_dpaa2_qdma.a
CC ifpga_feature_dev.o
CC ifpga_fme.o
CC ifpga_fme_iperf.o
CC ifpga_fme_dperf.o
CC ifpga_fme_error.o
CC ifpga_port.o
CC ifpga_port_error.o
CC opae_hw_api.o
CC opae_ifpga_hw_api.o
CC opae_debug.o
CC ifpga_fme_pr.o
CC ifpga_rawdev.o
--
== Build app/test-pmd
== Build app/proc-info
CC main.o
CC testpmd.o
/tmp/CENTOS_K3.10.0_GCC4.8.5/i686-native-linuxapp-gcc/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c: In function ‘debug_tm’:
/tmp/CENTOS_K3.10.0_GCC4.8.5/i686-native-linuxapp-gcc/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c:957:3: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (unsigned int j = 0; j < n_leaf_nodes; j++) {
^
/tmp/CENTOS_K3.10.0_GCC4.8.5/i686-native-linuxapp-gcc/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c:957:3: note: use option -std=c99 or -std=gnu99 to compile your code
make[5]: *** [main.o] Error 1
make[4]: *** [proc-info] Error 2
*Failed Build #2:
OS: CENTOS
Target: x86_64-native-linuxapp-gcc-shared
INSTALL-LIB librte_pmd_dpaa2_qdma.so.2.1
CC ifpga_feature_dev.o
CC ifpga_fme.o
CC ifpga_fme_iperf.o
CC ifpga_fme_dperf.o
CC ifpga_fme_error.o
CC ifpga_port.o
CC ifpga_port_error.o
CC opae_hw_api.o
CC opae_ifpga_hw_api.o
CC opae_debug.o
CC ifpga_fme_pr.o
CC ifpga_rawdev.o
--
== Build app/proc-info
== Build app/test-pmd
CC main.o
CC testpmd.o
/tmp/CENTOS_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc-shared/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c: In function ‘debug_tm’:
/tmp/CENTOS_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc-shared/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c:957:3: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (unsigned int j = 0; j < n_leaf_nodes; j++) {
^
/tmp/CENTOS_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc-shared/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c:957:3: note: use option -std=c99 or -std=gnu99 to compile your code
make[5]: *** [main.o] Error 1
make[4]: *** [proc-info] Error 2
*Failed Build #3:
OS: CENTOS
Target: x86_64-native-linuxapp-gcc
AR librte_pmd_dpaa2_qdma.a
INSTALL-LIB librte_pmd_dpaa2_qdma.a
CC ifpga_fme.o
CC ifpga_fme_iperf.o
CC ifpga_fme_dperf.o
CC ifpga_fme_error.o
CC ifpga_port.o
CC ifpga_port_error.o
CC opae_hw_api.o
CC opae_ifpga_hw_api.o
CC opae_debug.o
CC ifpga_fme_pr.o
CC ifpga_rawdev.o
--
== Build app/test-pmd
== Build app/proc-info
CC main.o
CC testpmd.o
/tmp/CENTOS_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c: In function ‘debug_tm’:
/tmp/CENTOS_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c:957:3: error: ‘for’ loop initial declarations are only allowed in C99 mode
for (unsigned int j = 0; j < n_leaf_nodes; j++) {
^
/tmp/CENTOS_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/037c135c335048c7988573278b7c979f/dpdk/app/proc-info/main.c:957:3: note: use option -std=c99 or -std=gnu99 to compile your code
make[5]: *** [main.o] Error 1
make[4]: *** [proc-info] Error 2
DPDK STV team
reply other threads:[~2018-10-23 14:12 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='0590c7$316e56@orsmga001.jf.intel.com' \
--to=sys_stv@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).