Test-Label: Intel-compilation Test-Status: FAILURE http://dpdk.org/patch/27580 _Compilation issues_ Submitter: Santosh Shukla Date: Mon, 14 Aug 2017 20:45:34 +0530 DPDK git baseline: Repo:dpdk, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd Patch27577-27580 --> compile error Build Summary: 21 Builds Done, 18 Successful, 3 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-clang i686-native-linuxapp-gcc x86_64-native-linuxapp-gcc x86_64-native-linuxapp-gcc-shared x86_64-native-linuxapp-gcc-debug 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: FreeBSD10.3_64 Target: x86_64-native-bsdapp-clang /home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_memory.c:76:19: error: no member named 'phys_addr' in 'struct rte_memseg' mcfg->memseg[0].phys_addr = (iova_addr_t)(uintptr_t)addr; ~~~~~~~~~~~~~~~ ^ /home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_memory.c:117:9: error: no member named 'phys_addr' in 'struct rte_memseg' seg->phys_addr = physaddr; ~~~ ^ 2 errors generated. /home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'eal_memory.o' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'eal' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'bsdapp' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'librte_eal' failed /home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:76: 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 #2: OS: FreeBSD10.3_64 Target: x86_64-native-bsdapp-gcc /home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_memory.c: In function 'rte_eal_hugepage_init': /home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_memory.c:76:18: error: 'struct rte_memseg' has no member named 'phys_addr' mcfg->memseg[0].phys_addr = (iova_addr_t)(uintptr_t)addr; ^ /home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_memory.c:117:7: error: 'struct rte_memseg' has no member named 'phys_addr' seg->phys_addr = physaddr; ^ /home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'eal_memory.o' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'eal' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'bsdapp' failed /home/patchWorkOrg/compilation/mk/rte.subdir.mk:63: recipe for target 'librte_eal' failed /home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:76: 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 #3: OS: CentOS7_64 Target: x86_64-native-linuxapp-clang In file included from /home/patchWorkOrg/compilation/lib/librte_kni/rte_kni.c:48: In file included from /home/patchWorkOrg/compilation/lib/librte_kni/rte_kni.h:53: /home/patchWorkOrg/compilation/x86_64-native-linuxapp-clang/include/exec-env/rte_kni_common.h:68:18: error: redefinition of typedef 'iova_addr_t' is a C11 feature [-Werror,-Wtypedef-redefinition] typedef uint64_t iova_addr_t; ^ /home/patchWorkOrg/compilation/x86_64-native-linuxapp-clang/include/rte_memory.h:101:18: note: previous definition is here typedef uint64_t iova_addr_t; /**< Physical address definition. */ ^ 1 error generated. DPDK STV team