Test-Label: Intel-compilation Test-Status: FAILURE http://dpdk.org/patch/26134 _Compilation issues_ Submitter: Pablo de Lara Date: Fri, 30 Jun 2017 10:51:09 +0100 DPDK git baseline: Repo:dpdk, Branch:master, CommitID:190ce8645e1ebeb0733f9dbc7fa854b50d1dac2e Patch26134-26134 --> compile error Build Summary: 21 Builds Done, 11 Successful, 10 Failures Test environment and configuration as below: OS: RHEL7.2_64 Kernel Version:3.10.0-514.10.2.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: UB1610_64 Kernel Version:4.8.0-22-generic CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz GCC Version:gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005 Clang Version:NA x86_64-native-linuxapp-icc 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: FC25_64 Kernel Version:4.8.6-300.fc25.x86_64 CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz GCC Version:gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1) 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.98-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: 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 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-debug x86_64-native-linuxapp-gcc-shared x86_64-native-linuxapp-gcc 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 Failed Build #1: OS: RHEL7.2_64 Target: i686-native-linuxapp-gcc /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_create’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_probe’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:490:3: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t’ [-Werror=format=] RTE_LOG(INFO, PMD, " workers core mask = %lx\n", ^ cc1: all warnings being treated as errors Failed Build #2: OS: RHEL7.2_64 Target: x86_64-native-linuxapp-gcc /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_create’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code Failed Build #3: OS: RHEL7.2_64 Target: x86_64-native-linuxapp-gcc-shared /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_create’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code Failed Build #4: OS: UB1604_64 Target: i686-native-linuxapp-gcc In file included from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_mempool.h:73:0, from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_mbuf.h:65, from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_crypto.h:48, from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_cryptodev.h:49, from /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:34: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_probe’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:491:22: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t {aka long long unsigned int}’ [-Werror=format=] init_params.wcmask); ^ /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_log.h:334:25: note: in definition of macro ‘RTE_LOG’ RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__) ^ cc1: all warnings being treated as errors /home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'scheduler_pmd.o' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'scheduler' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'crypto' 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 #5: OS: FreeBSD10.3_64 Target: x86_64-native-bsdapp-gcc /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function 'cryptodev_scheduler_create': /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: 'for' loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code /home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'scheduler_pmd.o' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'scheduler' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'crypto' 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 #6: OS: CentOS7_64 Target: i686-native-linuxapp-gcc /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_create’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_probe’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:490:3: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t’ [-Werror=format=] RTE_LOG(INFO, PMD, " workers core mask = %lx\n", ^ cc1: all warnings being treated as errors Failed Build #7: OS: CentOS7_64 Target: x86_64-native-linuxapp-gcc-shared /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_create’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code Failed Build #8: OS: CentOS7_64 Target: x86_64-native-linuxapp-gcc /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_create’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:132:3: note: use option -std=c99 or -std=gnu99 to compile your code Failed Build #9: OS: FC24_64 Target: i686-native-linuxapp-gcc In file included from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_mempool.h:73:0, from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_mbuf.h:65, from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_crypto.h:48, from /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_cryptodev.h:49, from /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:34: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c: In function ‘cryptodev_scheduler_probe’: /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c:491:22: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t {aka long long unsigned int}’ [-Werror=format=] init_params.wcmask); ^ /home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_log.h:334:25: note: in definition of macro ‘RTE_LOG’ RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__) ^ cc1: all warnings being treated as errors /home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'scheduler_pmd.o' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'scheduler' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'crypto' 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 #10: OS: RHEL7.3_64 Target: x86_64-native-linuxapp-icc /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c(132): error: type name is not allowed for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c(132): error: expected a ";" for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c(132): error #592: variable "i" is used before its value is set for (uint16_t i = 0; i < MAX_NB_WORKER_CORES; i++) { ^ compilation aborted for /home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_pmd.c (code 2) DPDK STV team