From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: sys_stv@intel.com, waterman.cao@intel.com
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com,
test-report@dpdk.org
Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (29/47)
Date: Wed, 23 Mar 2016 11:53:48 +0100 [thread overview]
Message-ID: <2097148.SushTU6EDT@xps13> (raw)
In-Reply-To: <0416cf$242sbk@fmsmga004.fm.intel.com>
2016-03-22 15:00, sys_stv@intel.com:
> Last commit Time : Tue Mar 22 20:46:53 2016 +0100
> Last Author : Thomas Monjalon
I am not the author. Please fix it.
The author is retrieved with git log -1 --format='%an'
> Failure #18
> OS : FC21_32 / 3.18.8-201
> Compiler : GCC 4.9.2
> Build Configuration: i686-native-linuxapp-gcc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y
>
> Makefile:54: *** The RTE_TARGET chosen is not compatible with this environment (x86_64), for this application. Please change the definition of the RTE_TARGET environment variable, or run the application on a 32-bit OS. Stop.
> DPDK/mk/rte.extsubdir.mk:46: recipe for target 'dpdk_qat' failed
> DPDK/mk/rte.sdkexamples.mk:52: recipe for target 'i686-native-linuxapp-gcc_examples' failed
> DPDK/mk/rte.sdkroot.mk:119: recipe for target 'examples' failed
Please put a clear separation between failures and success.
> UBT144_32 / Linux 3.13.0-30 / GCC 4.8.2
There are some double spaces here.
> Config: i686-native-linuxapp-gcc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y
This presentation is simple and good.
Why it is different in failure cases?
next prev parent reply other threads:[~2016-03-23 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 22:00 sys_stv
2016-03-23 10:53 ` Thomas Monjalon [this message]
2016-03-24 7:55 ` Liu, Yong
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=2097148.SushTU6EDT@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dpdk_sw_eng@intel.com \
--cc=npg.sw.core.tools.prc@intel.com \
--cc=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=waterman.cao@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).