From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw32568 [PATCH v1 6/6] net: fix rte_ether conflicts with libc
Date: 09 Jan 2018 20:40:23 -0800 [thread overview]
Message-ID: <b11803$8fe81@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7792 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32568
_Compilation issues_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Thu, 21 Dec 2017 14:00:04 +0100
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:f06125c07d6203a84e9b242c62d6a8e532a5c51d
Patch32563-32568 --> compile error
Build Summary: 16 Builds Done, 14 Successful, 2 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-gcc-debug
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
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
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: FreeBSD10.3_64
Target: x86_64-native-bsdapp-clang
SYMLINK-FILE include/rte_ethdev.h
SYMLINK-FILE include/rte_ethdev_pci.h
SYMLINK-FILE include/rte_ethdev_vdev.h
SYMLINK-FILE include/rte_eth_ctrl.h
SYMLINK-FILE include/rte_dev_info.h
SYMLINK-FILE include/rte_flow.h
SYMLINK-FILE include/rte_flow_driver.h
SYMLINK-FILE include/rte_tm.h
SYMLINK-FILE include/rte_tm_driver.h
SYMLINK-FILE include/rte_mtr.h
SYMLINK-FILE include/rte_mtr_driver.hIn file included from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.c:42:
In file included from /home/patchWorkOrg/compilation/lib/librte_ether/rte_ethdev.h:157:
In file included from /home/patchWorkOrg/compilation/x86_64-native-bsdapp-clang/include/rte_ether.h:18:
/usr/include/net/ethernet.h:61:2: error: unknown type name 'u_char'; did you mean 'char'?
u_char ether_dhost[ETHER_ADDR_LEN];
^
/usr/include/net/ethernet.h:62:2: error: unknown type name 'u_char'; did you mean 'char'?
u_char ether_shost[ETHER_ADDR_LEN];
^
/usr/include/net/ethernet.h:63:2: error: unknown type name 'u_short'; did you mean 'short'?
u_short ether_type;
^
/usr/include/net/ethernet.h:70:2: error: unknown type name 'u_char'; did you mean 'char'?
u_char octet[ETHER_ADDR_LEN];
^
4 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:110: recipe for target 'rte_flow.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_ether' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: 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:79: recipe for target 'install' failed
Failed Build #2:
OS: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
SYMLINK-FILE include/rte_ethdev.h
SYMLINK-FILE include/rte_ethdev_pci.h
SYMLINK-FILE include/rte_ethdev_vdev.h
SYMLINK-FILE include/rte_eth_ctrl.h
SYMLINK-FILE include/rte_dev_info.h
SYMLINK-FILE include/rte_flow.h
SYMLINK-FILE include/rte_flow_driver.h
SYMLINK-FILE include/rte_tm.h
SYMLINK-FILE include/rte_tm_driver.h
SYMLINK-FILE include/rte_mtr.h
SYMLINK-FILE include/rte_mtr_driver.hIn file included from /home/patchWorkOrg/compilation/x86_64-native-bsdapp-gcc/include/rte_ether.h:18:0,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_ethdev.h:157,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.c:42:
/usr/include/net/ethernet.h:61:2: error: unknown type name 'u_char'
u_char ether_dhost[ETHER_ADDR_LEN];
^
/usr/include/net/ethernet.h:62:2: error: unknown type name 'u_char'
u_char ether_shost[ETHER_ADDR_LEN];
^
/usr/include/net/ethernet.h:63:2: error: unknown type name 'u_short'
u_short ether_type;
^
/usr/include/net/ethernet.h:70:2: error: unknown type name 'u_char'
u_char octet[ETHER_ADDR_LEN];
^
In file included from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow_driver.h:49:0,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.c:43:
/home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.h:485:2: error: wide character array initialized from non-wide string
.dst.addr_bytes = "\xff\xff\xff\xff\xff\xff",
^
/home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.h:485:2: error: (near initialization for 'rte_flow_item_eth_mask.dst.octet')
/home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.h:486:2: error: missing initializer for field 'octet' of 'struct ether_addr' [-Werror=missing-field-initializers]
.src.addr_bytes = "\xff\xff\xff\xff\xff\xff",
^
In file included from /home/patchWorkOrg/compilation/x86_64-native-bsdapp-gcc/include/rte_ether.h:18:0,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_ethdev.h:157,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.c:42:
/usr/include/net/ethernet.h:70:9: note: 'octet' declared here
u_char octet[ETHER_ADDR_LEN];
^
In file included from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow_driver.h:49:0,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.c:43:
/home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.h:486:2: error: wide character array initialized from non-wide string
.src.addr_bytes = "\xff\xff\xff\xff\xff\xff",
^
/home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.h:486:2: error: (near initialization for 'rte_flow_item_eth_mask.src.octet')
/home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.h:487:2: error: missing initializer for field 'octet' of 'struct ether_addr' [-Werror=missing-field-initializers]
.type = RTE_BE16(0x0000),
^
In file included from /home/patchWorkOrg/compilation/x86_64-native-bsdapp-gcc/include/rte_ether.h:18:0,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_ethdev.h:157,
from /home/patchWorkOrg/compilation/lib/librte_ether/rte_flow.c:42:
/usr/include/net/ethernet.h:70:9: note: 'octet' declared here
u_char octet[ETHER_ADDR_LEN];
^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:110: recipe for target 'rte_flow.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_ether' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: 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:79: recipe for target 'install' failed
DPDK STV team
reply other threads:[~2018-01-10 4:40 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='b11803$8fe81@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=adrien.mazarguil@6wind.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).