From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw32456 [PATCH RFC v2 02/23] eal: add function to report number of detected sockets
Date: 09 Jan 2018 01:15:02 -0800 [thread overview]
Message-ID: <1f4ae4$ofifi@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6063 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32456
_Compilation issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tue, 19 Dec 2017 11:14:41 +0000
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:7c6790df680d7fe3bb491e412da3cb689803bc71
Patch32452-32456 --> compile error
Build Summary: 16 Builds Done, 13 Successful, 3 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-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-81-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
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
Failed Build #1:
OS: FC24_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/exec-env/rte_kni_common.h/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c: In function ‘map_all_hugepages’:
/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:399:42: error: passing argument 2 of ‘eal_get_virtual_area’ from incompatible pointer type [-Werror=incompatible-pointer-types]
vma_addr = eal_get_virtual_area(NULL, &vma_len,
^
In file included from /home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:70:0:
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_private.h:224:1: note: expected ‘uint64_t * {aka long long unsigned int *}’ but argument is of type ‘size_t * {aka unsigned int *}’
eal_get_virtual_area(void *requested_addr, uint64_t *size,
^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:110: recipe for target 'eal_memory.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'eal' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'linuxapp' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_eal' 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: UB1604_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/exec-env/rte_kni_common.h/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c: In function ‘map_all_hugepages’:
/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:399:42: error: passing argument 2 of ‘eal_get_virtual_area’ from incompatible pointer type [-Werror=incompatible-pointer-types]
vma_addr = eal_get_virtual_area(NULL, &vma_len,
^
In file included from /home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:70:0:
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_private.h:224:1: note: expected ‘uint64_t * {aka long long unsigned int *}’ but argument is of type ‘size_t * {aka unsigned int *}’
eal_get_virtual_area(void *requested_addr, uint64_t *size,
^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:110: recipe for target 'eal_memory.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'eal' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'linuxapp' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_eal' 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 #3:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/exec-env/rte_kni_common.h/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c: In function ‘map_all_hugepages’:
/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:401:6: error: passing argument 2 of ‘eal_get_virtual_area’ from incompatible pointer type [-Werror]
EAL_VIRTUAL_AREA_ALLOW_SHRINK);
^
In file included from /home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:70:0:
/home/patchWorkOrg/compilation/lib/librte_eal/common/eal_private.h:224:1: note: expected ‘uint64_t *’ but argument is of type ‘size_t *’
eal_get_virtual_area(void *requested_addr, uint64_t *size,
^
cc1: all warnings being treated as errors
DPDK STV team
reply other threads:[~2018-01-09 9:15 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='1f4ae4$ofifi@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=anatoly.burakov@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).