From: "Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/test-crypto-perf: fix gcc compilation under FreeBSD
Date: Thu, 2 Feb 2017 15:18:30 +0000 [thread overview]
Message-ID: <7ADD74816B4C8A45B56203CBA65FE5A637848817@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <3122931.ok1ldL3Xjz@xps13>
>-----Original Message-----
>From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
>Sent: Thursday, February 02, 2017 2:57 PM
>To: Mrzyglod, DanielX T <danielx.t.mrzyglod@intel.com>; Mrozowicz, SlawomirX
><slawomirx.mrozowicz@intel.com>; De Lara Guarch, Pablo
><pablo.de.lara.guarch@intel.com>
>Cc: dev@dpdk.org
>Subject: Re: [dpdk-dev] [PATCH v2] app/test-crypto-perf: fix gcc compilation
>under FreeBSD
>
>Hi,
>
>The error is not specific to GCC.
>I can reproduce it with x86_64-native-bsdapp-clang.
>
I can reproduce it only at FreeBSD 10.3 gcc48
I have mindblow about it.
When you see patchwork report:
http://dpdk.org/dev/patchwork/patch/19998/ - Everything is ok.
But it isn't due to daily raport: http://dpdk.org/ml/archives/test-report/2017-January/010203.html
For clang it was working so I prepared patch for gcc.
>2017-02-02 14:41, Daniel Mrzyglod:
>> This patch fixes error: implicit declaration of function 'getline'
>>
>> Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test
>application")
>>
>> Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
>
>I am interested to understand how such error can happen with the
>recent integration of build checks in patchwork.
>Have you received any automatic mail about the compilation error?
>Do you think setting colors (green/orange/red) in the columns S/W/F
>would help?
We didn't get any error raport about this patchseries - so I think there may be some errors in DPDK's patchwork build environment .
Everybody like colors but it's not critical :>
next prev parent reply other threads:[~2017-02-02 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 13:31 [dpdk-dev] [PATCH] " Daniel Mrzyglod
2017-02-02 10:52 ` De Lara Guarch, Pablo
2017-02-02 13:41 ` [dpdk-dev] [PATCH v2] " Daniel Mrzyglod
2017-02-02 13:56 ` Thomas Monjalon
2017-02-02 15:18 ` Mrzyglod, DanielX T [this message]
2017-02-03 11:31 ` De Lara Guarch, Pablo
2017-02-03 12:09 ` Mrzyglod, DanielX T
2017-02-06 13:24 ` De Lara Guarch, Pablo
2017-02-07 9:44 ` [dpdk-dev] [PATCH v3] app/test-crypto-perf: fix " Daniel Mrzyglod
2017-02-09 15:22 ` Thomas Monjalon
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=7ADD74816B4C8A45B56203CBA65FE5A637848817@IRSMSX107.ger.corp.intel.com \
--to=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=slawomirx.mrozowicz@intel.com \
--cc=thomas.monjalon@6wind.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).