From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/iptraf-ng: really add _GNU_SOURCE in CFLAGS
Date: Sat, 28 May 2016 15:52:02 +0200 [thread overview]
Message-ID: <20160528155202.77779355@free-electrons.com> (raw)
In-Reply-To: <1464441352-24940-1-git-send-email-romain.naour@gmail.com>
Hello,
On Sat, 28 May 2016 15:15:52 +0200, Romain Naour wrote:
> When iptraf-ng is build with musl, it needs _GNU_SOURCE in CFLAGS to define
> the content of "struct tcphdr".
>
> iptraf-ng.mk try to add _GNU_SOURCE in CFLAGS but it's not taken into account.
>
> Add it using IPTRAF_NG_CONF_ENV instead of IPTRAF_NG_MAKE_ENV.
>
> Fixes:
> http://autobuild.buildroot.net/results/a1b/a1b18f2e3d075d349c19536a7c5553f24b75a323
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> package/iptraf-ng/iptraf-ng.mk | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-28 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 13:15 [Buildroot] [PATCH] package/iptraf-ng: really add _GNU_SOURCE in CFLAGS Romain Naour
2016-05-28 13:52 ` Thomas Petazzoni [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=20160528155202.77779355@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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