From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jia.guo@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36674 [PATCH V17 4/4] app/testpmd: enable device hotplug monitoring
Date: 29 Mar 2018 13:08:15 -0700 [thread overview]
Message-ID: <ca5293$18f7na@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6895 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36674
_Compilation issues_
Submitter: Guo Jia <jia.guo@intel.com>
Date: Fri, 30 Mar 2018 00:00:02 +0800
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:20526313ba41174d3e7831ee800f6e938a1d5b85
Patch36671-36674 --> compile error
Build Summary: 15 Builds Done, 9 Successful, 6 Failures
Test environment and configuration as below:
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-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-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_dev.c:7:23: error: expected ';' after top level declarator
int __rte_experimental
^
;
1 error generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'eal_dev.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 'bsdapp' 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: FreeBSD10.3_64
Target: x86_64-native-bsdapp-gcc
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_dev.c:8:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'rte_dev_event_monitor_start'
rte_dev_event_monitor_start(void)
^
/home/patchWorkOrg/compilation/lib/librte_eal/bsdapp/eal/eal_dev.c:15:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'rte_dev_event_monitor_stop'
rte_dev_event_monitor_stop(void)
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'eal_dev.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 'bsdapp' 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: FC24_64
Target: x86_64-native-linuxapp-gcc-shared
testpmd.o: In function `pmd_test_exit':
testpmd.c:(.text+0x3c64): undefined reference to `rte_dev_event_monitor_stop'
testpmd.o: In function `main':
testpmd.c:(.text.startup+0x4b7): undefined reference to `rte_dev_event_monitor_start'
collect2: error: ld returned 1 exit status
/home/patchWorkOrg/compilation/mk/rte.app.mk:343: recipe for target 'testpmd' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'test-pmd' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'app' 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 #4:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc-shared
testpmd.o: In function `pmd_test_exit':
testpmd.c:(.text+0x3ecd): undefined reference to `rte_dev_event_monitor_stop'
testpmd.o: In function `main':
testpmd.c:(.text.startup+0x4cd): undefined reference to `rte_dev_event_monitor_start'
collect2: error: ld returned 1 exit status
/home/patchWorkOrg/compilation/mk/rte.app.mk:343: recipe for target 'testpmd' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'test-pmd' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'app' 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 #5:
OS: CentOS7_64
Target: x86_64-native-linuxapp-clang
In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_portal.c:7:
In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_portal.h:7:
In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_sys.h:21:
In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_sys_decl.h:7:
/home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/include/fsl_qbman_base.h:9:19: error: redefinition of typedef 'dma_addr_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
typedef uint64_t dma_addr_t;
^
/home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/include/compat.h:35:18: note: previous definition is here
typedef uint64_t dma_addr_t;
^
1 error generated.
Failed Build #6:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared
testpmd.o: In function `pmd_test_exit':
testpmd.c:(.text+0x3c78): undefined reference to `rte_dev_event_monitor_stop'
testpmd.o: In function `main':
testpmd.c:(.text.startup+0x4ec): undefined reference to `rte_dev_event_monitor_start'
collect2: error: ld returned 1 exit status
DPDK STV team
reply other threads:[~2018-03-29 20:08 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='ca5293$18f7na@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jia.guo@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).