From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw38138[dpdk-dev, v7, 15/22] bus/pci: add device matching field id
Date: 20 Apr 2018 03:37:27 -0700 [thread overview]
Message-ID: <0590c7$1f4b1u@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5607 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38138
_Compilation issues_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: 2018-04-15 15:07:44
DPDK git baseline: Repo:dpdk-master, CommitID: 08efcf533f6a1dc5b12bcf1d5ded83743b8d5cc4
Build Summary: 15 Builds Done, 12 Successful, 3 Failures
Test environment and configuration as below:
OS: FC25
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 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-debug
OS: FC24
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 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc-shared
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: CENTOS
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 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
OS: UB1604
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.9) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: FreeBSD
Kernel Version: 10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.75-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 4.8.5
Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
*Failed Build #1:
OS: UB1604
Target: x86_64-native-linuxapp-gcc-shared
rte_kvargs.o: In function `rte_kvargs_parse':
rte_kvargs.c:(.text+0x278): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x3bf): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x3ee): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x40b): undefined reference to `rte_log'
collect2: error: ld returned 1 exit status
/tmp/UB1604_K4.4.0_GCC5.4.0/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.lib.mk:98: recipe for target 'librte_kvargs.so.1.1' failed
make[5]: *** [librte_kvargs.so.1.1] Error 1
/tmp/UB1604_K4.4.0_GCC5.4.0/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_kvargs' failed
make[4]: *** [librte_kvargs] Error 2
/tmp/UB1604_K4.4.0_GCC5.4.0/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkbuild.mk:49: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/tmp/UB1604_K4.4.0_GCC5.4.0/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
make[2]: *** [all] Error 2
/tmp/UB1604_K4.4.0_GCC5.4.0/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/tmp/UB1604_K4.4.0_GCC5.4.0/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
make: *** [install] Error 2
*Failed Build #2:
OS: CENTOS
Target: x86_64-native-linuxapp-gcc-shared
rte_kvargs.o: In function `rte_kvargs_parse':
rte_kvargs.c:(.text+0x276): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x3b7): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x3fa): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x415): undefined reference to `rte_log'
collect2: error: ld returned 1 exit status
make[5]: *** [librte_kvargs.so.1.1] Error 1
make[4]: *** [librte_kvargs] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
*Failed Build #3:
OS: FC24
Target: x86_64-native-linuxapp-gcc-shared
rte_kvargs.o: In function `rte_kvargs_parse':
rte_kvargs.c:(.text+0x298): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x3e7): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x402): undefined reference to `rte_log'
rte_kvargs.c:(.text+0x41f): undefined reference to `rte_log'
collect2: error: ld returned 1 exit status
/tmp/FC24_K4.9.13_GCC6.2.1/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.lib.mk:98: recipe for target 'librte_kvargs.so.1.1' failed
make[5]: *** [librte_kvargs.so.1.1] Error 1
/tmp/FC24_K4.9.13_GCC6.2.1/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_kvargs' failed
make[4]: *** [librte_kvargs] Error 2
/tmp/FC24_K4.9.13_GCC6.2.1/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkbuild.mk:49: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/tmp/FC24_K4.9.13_GCC6.2.1/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
make[2]: *** [all] Error 2
/tmp/FC24_K4.9.13_GCC6.2.1/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/tmp/FC24_K4.9.13_GCC6.2.1/x86_64-native-linuxapp-gcc-shared/97633bfdd660439db768f67886b01fc6/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
make: *** [install] Error 2
DPDK STV team
reply other threads:[~2018-04-20 10:37 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='0590c7$1f4b1u@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).