[dpdk-test-report] |FAILURE| pw24292 [PATCH] cryptodev: remove crypto device type enumeration

automatic DPDK test reports
 help / color / mirror / Atom feed

From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: slawomirx.mrozowicz@intel.com
Subject: [dpdk-test-report] |FAILURE| pw24292 [PATCH] cryptodev: remove crypto device type enumeration
Date: 15 May 2017 03:36:37 -0700	[thread overview]
Message-ID: <ffb989$2iqt0h@orsmga002.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 7717 bytes --]

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

http://dpdk.org/patch/24292

_Compilation issues_

Submitter: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Date: Mon, 15 May 2017 11:55:42 +0200
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:4155e1323262459c3401bc97f974f52ec3017a21

Patch24292-24292 --> 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-gcc
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-clang
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-debug
    i686-native-linuxapp-gcc
    x86_64-native-linuxapp-clang
    x86_64-native-linuxapp-gcc-shared
    x86_64-native-linuxapp-gcc
OS: UB1604_64
    Kernel Version:4.4.0-64-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

Failed Build #1:
OS: RHEL7.2_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c: In function ‘rte_cryptodev_driver_id_get’:
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: note: use option -std=c99 or -std=gnu99 to compile your code


Failed Build #2:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c: In function ‘rte_cryptodev_driver_id_get’:
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: 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/lib/librte_cryptodev/rte_cryptodev.c: In function ‘rte_cryptodev_driver_id_get’:
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: note: use option -std=c99 or -std=gnu99 to compile your code


Failed Build #4:
OS: RHEL7.3_64
Target: x86_64-native-linuxapp-icc
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c(1585): error: type name is not allowed
  	for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  	     ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c(1585): error: expected a ";"
  	for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  	             ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c(1585): error: identifier "id" is undefined
  	for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  	                     ^
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/lib/librte_cryptodev/rte_cryptodev.c: In function 'rte_cryptodev_driver_id_get':
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: 'for' loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: 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 'rte_cryptodev.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'librte_cryptodev' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:73: recipe for target 'lib' 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/lib/librte_cryptodev/rte_cryptodev.c: In function ‘rte_cryptodev_driver_id_get’:
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: note: use option -std=c99 or -std=gnu99 to compile your code


Failed Build #7:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c: In function ‘rte_cryptodev_driver_id_get’:
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: note: use option -std=c99 or -std=gnu99 to compile your code


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

/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c: In function ‘rte_cryptodev_driver_id_get’:
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: error: ‘for’ loop initial declarations are only allowed in C99 mode
  for (uint8_t id = 0; id < rte_cryptodev_driver_id; id++)
  ^
/home/patchWorkOrg/compilation/lib/librte_cryptodev/rte_cryptodev.c:1585:2: note: use option -std=c99 or -std=gnu99 to compile your code


DPDK STV team

                 reply	other threads:[~2017-05-15 10:36 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='ffb989$2iqt0h@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=slawomirx.mrozowicz@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).