From: "Liu, Yu Y" <yu.y.liu@intel.com>
To: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
Jan Medala <jan@semihalf.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Cao, Waterman" <waterman.cao@intel.com>,
"Chen, WeichunX" <weichunx.chen@intel.com>,
"Xu, HuilongX" <huilongx.xu@intel.com>,
"Glynn, Michael J" <michael.j.glynn@intel.com>,
"Gu, YongjieX" <yongjiex.gu@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] dpdk daily build error on dpdk16.07-rc2
Date: Thu, 14 Jul 2016 11:34:33 +0000 [thread overview]
Message-ID: <D9E7459352598649B9DF0563CBC90AEB39F9ED68@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <E1E7EC9273ACA248A8E9BE46A66CE0A03EBCE21C@SHSMSX101.ccr.corp.intel.com>
Hi Thomas,
Would you check who can work on "dpdk16.07-rc2 compile error on FC18 & UB1204"?
For "dpdk16.07-rc2 compile error on suse11", I saw document shows we support suse12+. Seems it is not issue for this release.
Agree?
Thanks & Regards,
Yu Liu
From: Gu, YongjieX
Sent: Thursday, July 14, 2016 5:23 PM
To: thomas.monjalon@6wind.com; Richardson, Bruce <bruce.richardson@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Gonzalez Monroy, Sergio <sergio.gonzalez.monroy@intel.com>; Jan Medala <jan@semihalf.com>; dev@dpdk.org
Cc: Cao, Waterman <waterman.cao@intel.com>; Liu, Yu Y <yu.y.liu@intel.com>; Chen, WeichunX <weichunx.chen@intel.com>; Xu, HuilongX <huilongx.xu@intel.com>; Gu, YongjieX <yongjiex.gu@intel.com>
Subject: dpdk daily build error on dpdk16.07-rc2
Hi,All,
There are 4 build errors reported by our dpdk daily report,and can you take a look on these issues.
Jan is working on ena issues,and I will help to test it.
OS, Kernel , GCC , ICC
Affected Targets
Build errors
comments
FC18_64,3.6.10-4,4.7.2,14.0.0
x86_64-ivshmem-linuxapp-gcc
CC test_kvargs.o
UBT124_64,3.8.0-29,4.6.3,14.0.0
LD test
SUSE11SP2_64,3.0.13-0,4.5.1,14.0.0
/jenkins/workspace/DPDK_AUTO_IDT_VM_FC18_64_BUILD2/DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `eal_alarm_callback':
eal_alarm.c:(.text+0xd7): undefined reference to `clock_gettime'
/jenkins/workspace/DPDK_AUTO_IDT_VM_FC18_64_BUILD2/DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `rte_eal_alarm_set':
eal_alarm.c:(.text+0x20f): undefined reference to `clock_gettime'
/jenkins/workspace/DPDK_AUTO_IDT_VM_FC18_64_BUILD2/DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_timer.o): In function `get_tsc_freq':
eal_timer.c:(.text+0x108): undefined reference to `clock_gettime'
eal_timer.c:(.text+0x146): undefined reference to `clock_gettime'
collect2: error: ld returned 1 exit status
make[5]: *** [test] Error 1
make[4]: *** [test] Error 2
make[3]: *** [app] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2
SUSE11SP2_64,3.0.13-0,4.5.1,14.0.0
x86_64-native-linuxapp-gcc-examples
== ipsec-secgw
CC ipsec.o
CC esp.o
CC sp4.o
CC sp6.o
CC sa.o
/jenkins/workspace/DPDK_AUTO_IDT_VM_SUSE11SP2_64_BUILD/DPDK/examples/ipsec-secgw/sa.c:56:2: error: unknown field 'ip4' specified in initializer
compilation terminated due to -Wfatal-errors.
make[4]: *** [sa.o] Error 1
make[3]: *** [all] Error 2
make[2]: *** [ipsec-secgw] Error 2
make[1]: *** [x86_64-native-linuxapp-gcc_examples] Error 2
make: *** [examples] Error 2
x86_64-native-linuxapp-icc-examples
== ipsec-secgw
x86_64-ivshmem-linuxapp-icc-examples
CC ipsec.o
CC esp.o
CC sp4.o
CC sp6.o
CC sa.o
icc: command line warning #10158: ignoring option '-diag-disable'; argument must be separate
/jenkins/workspace/DPDK_AUTO_IDT_VM_SUSE11SP2_64_BUILD/DPDK/examples/ipsec-secgw/sa.c(56): error: a designator for an anonymous union member can only appear within braces corresponding to that anonymous union
.src.ip4 = IPv4(172, 16, 1, 5),
^
compilation aborted for /jenkins/workspace/DPDK_AUTO_IDT_VM_SUSE11SP2_64_BUILD/DPDK/examples/ipsec-secgw/sa.c (code 4)
make[4]: *** [sa.o] Error 4
make[3]: *** [all] Error 2
make[2]: *** [ipsec-secgw] Error 2
make[1]: *** [x86_64-native-linuxapp-icc_examples] Error 2
make: *** [examples] Error 2
UBT144_32,3.13.0-30,4.8.2,14.0.0
i686-native-linuxapp-icc
== Build drivers/net/ena
CC ena_ethdev.o
PMDINFO ena_ethdev.o.pmd.c
CC ena_ethdev.o.pmd.o
LD ena_ethdev.o
CC ena_com.o
/jenkins/workspace/DPDK_AUTO_IDT_VM_UBT144_32_BUILD/DPDK/drivers/net/ena/base/ena_com.c(346): error #3656: variable "dev_node" may be used before its value is set
ENA_MEM_ALLOC_COHERENT_NODE(ena_dev->dmadev,
^
compilation aborted for /jenkins/workspace/DPDK_AUTO_IDT_VM_UBT144_32_BUILD/DPDK/drivers/net/ena/base/ena_com.c (code 4)
make[6]: *** [ena_com.o] Error 4
make[5]: *** [ena] Error 2
make[4]: *** [net] Error 2
make[3]: *** [drivers] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2
freebsd10.3,10.3-RELEASE,4.8.5
x86_64-native-linuxapp-gcc
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
sed: 1: "/usr/home/xugang/dpdk-1 ...": extra characters at the end of h command
^C/usr/home/xugang/dpdk-16.07-rc2/mk/rte.sdkconfig.mk:87: recipe for target '/usr/home/xugang/dpdk-16.07-rc
gmake[3]: *** [/usr/home/xugang/dpdk-16.07-rc2/x86_64-native-bsdapp-gcc/.config] Interrupt
/usr/home/xugang/dpdk-16.07-rc2/mk/rte.sdkroot.mk:90: recipe for target 'config' failed
gmake[2]: *** [config] Interrupt
/usr/home/xugang/dpdk-16.07-rc2/mk/rte.sdkinstall.mk:84: recipe for target 'pre_install' failed
gmake[1]: *** [pre_install] Interrupt
/usr/home/xugang/dpdk-16.07-rc2/mk/rte.sdkroot.mk:98: recipe for target 'install' failed
gmake: *** [install] Interrupt
Thanks
Yongie
next prev parent reply other threads:[~2016-07-14 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 9:23 Gu, YongjieX
2016-07-14 11:34 ` Liu, Yu Y [this message]
2016-07-14 12:48 ` Thomas Monjalon
2016-07-15 11:13 ` Liu, Yu Y
2016-07-15 11:17 ` Jan Mędala
2016-07-19 10:27 ` Liu, Yu Y
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=D9E7459352598649B9DF0563CBC90AEB39F9ED68@SHSMSX101.ccr.corp.intel.com \
--to=yu.y.liu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=huilongx.xu@intel.com \
--cc=jan@semihalf.com \
--cc=michael.j.glynn@intel.com \
--cc=reshma.pattan@intel.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=waterman.cao@intel.com \
--cc=weichunx.chen@intel.com \
--cc=yongjiex.gu@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).