From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>,
slawomirx.mrozowicz@intel.com, 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
Date: Thu, 02 Feb 2017 14:56:51 +0100 [thread overview]
Message-ID: <3122931.ok1ldL3Xjz@xps13> (raw)
In-Reply-To: <1486042866-135177-1-git-send-email-danielx.t.mrzyglod@intel.com>
Hi,
The error is not specific to GCC.
I can reproduce it with x86_64-native-bsdapp-clang.
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?
next prev parent reply other threads:[~2017-02-02 13:56 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 [this message]
2017-02-02 15:18 ` Mrzyglod, DanielX T
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=3122931.ok1ldL3Xjz@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=slawomirx.mrozowicz@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).