Test-Label: Intel-compilation
Test-Status: FAILURE

http://dpdk.org/patch/26650

_Compilation issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri,  7 Jul 2017 12:52:49 -0700
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:18da437b5f637365c4a28dcac7d1bae73ebad91c

Patch26650-26650 --> compile error
Build Summary: 21 Builds Done, 13 Successful, 8 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: 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: 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-gcc
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-gcc-debug
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-clang
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

Failed Build #1:
OS: RHEL7.2_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_stop’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_create_private_ctx’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^


Failed Build #2:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_stop’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_create_private_ctx’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^


Failed Build #3:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_stop’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_create_private_ctx’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^


Failed Build #4:
OS: RHEL7.3_64
Target: x86_64-native-linuxapp-icc
^
compilation aborted for /home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c (code 2)


Failed Build #5:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function 'scheduler_stop':
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: 'for' loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function 'scheduler_create_private_ctx':
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: 'for' loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'scheduler_multicore.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_multicore.c: In function ‘scheduler_stop’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_create_private_ctx’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^


Failed Build #7:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_stop’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_create_private_ctx’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^


Failed Build #8:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_stop’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
  ^
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:286:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c: In function ‘scheduler_create_private_ctx’:
/home/patchWorkOrg/compilation/drivers/crypto/scheduler/scheduler_multicore.c:331:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint16_t i = 0; i < sched_ctx->nb_wc; i++) {
  ^


DPDK STV team