From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>,
"Wei, FangfangX" <fangfangx.wei@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Xu, Qian Q" <qian.q.xu@intel.com>,
"Liu, Yong" <yong.liu@intel.com>,
"Chen, WeichunX" <weichunx.chen@intel.com>,
"Lu, PeipeiX" <peipeix.lu@intel.com>,
"Xu, HuilongX" <huilongx.xu@intel.com>,
DPDK_SW_ENG <dpdk_sw_eng@intel.com>
Subject: Re: [dpdk-dev] FW: [dpdk-test-report] | ERROR | daily Intel builds (46/55)
Date: Thu, 6 Apr 2017 10:04:36 +0100 [thread overview]
Message-ID: <e2e2cae4-bd6d-bb60-ea85-c1e162c92b90@intel.com> (raw)
In-Reply-To: <20170406105707.61477426@paques.dev.6wind.com>
On 4/6/2017 9:57 AM, Pascal Mazon wrote:
> Hi,
>
> I'll take a look at the tap issue.
Thanks Pascal,
And I can check thunderx and #5.
>
> Best regards,
> Pascal
>
> On Thu, 6 Apr 2017 08:03:46 +0000
> "Wei, FangfangX" <fangfangx.wei@intel.com> wrote:
>
>> Hi all,
>>
>> There're 3 new issues in daily build report:
>> 1. Failure #1, #2, error logs as below:
>> == Build drivers/net/thunderx
>> CC nicvf_rxtx.o
>> cc1: error: invalid option argument ‘-Ofast’
>> make[6]: *** [nicvf_rxtx.o] Error 1
>> make[5]: *** [thunderx] 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
>>
>> It occurred by following commit:
>> commit 0bc8874b3b2c2da74bb955ce2de2da7eb009a8bf
>> Author: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>> Date: Sun Mar 19 20:18:48 2017 +0530
>>
>> config: enable thunderx nicvf
>>
>> 2. Failure #3, #4, #6, #7, #8, #9, error logs as below:
>> /homeDPDK/drivers/net/tap/rte_eth_tap.c:78:0: error: "RTE_PMD_TAP_MAX_QUEUES" redefined [-Werror] compilation terminated due to -Wfatal-errors.
>> cc1: all warnings being treated as errors
>>
>> It occurred by following commit:
>> commit cf5643661161056c0ad0c073dd37ff674c2c9dc6
>> Author: Pascal Mazon <pascal.mazon@6wind.com>
>> Date: Thu Mar 23 09:33:54 2017 +0100
>>
>> net/tap: move private elements to external header
>>
>>
>> 3. Failure #5, I'm still debugging it.
>>
>> Best Regards
>> Fangfang Wei
>>
<...>
prev parent reply other threads:[~2017-04-06 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15e752$p3b6qk@FMSMGA003.fm.intel.com>
2017-04-06 8:03 ` Wei, FangfangX
2017-04-06 8:57 ` Pascal Mazon
2017-04-06 9:04 ` Ferruh Yigit [this message]
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=e2e2cae4-bd6d-bb60-ea85-c1e162c92b90@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dpdk_sw_eng@intel.com \
--cc=fangfangx.wei@intel.com \
--cc=huilongx.xu@intel.com \
--cc=pascal.mazon@6wind.com \
--cc=peipeix.lu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=weichunx.chen@intel.com \
--cc=yong.liu@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).