All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/iptraf-ng: Fix musl build
Date: Wed, 30 Mar 2016 22:44:23 +0200	[thread overview]
Message-ID: <1459370663.1257.3.camel@embedded.rocks> (raw)
In-Reply-To: <1453586622-21700-1-git-send-email-bernd.kuhls@t-online.de>

Hi,

On Sa, 2016-01-23 at 23:03 +0100, Bernd Kuhls wrote:
> Ported from
> http://git.alpinelinux.org/cgit/aports/tree/main/iptraf-ng/APKBUILD#n
> 28
> 
> Fixes
> http://autobuild.buildroot.net/results/72b/72b019ce5bb52b8b87d92cce67
> 5708f7b9f8a96e/
> http://autobuild.buildroot.net/results/f67/f67f1c2a627a6d535dd5c00e2e
> e131b5c5a99a0a/
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> ?package/iptraf-ng/iptraf-ng.mk | 1 +
> ?1 file changed, 1 insertion(+)
> 
> diff --git a/package/iptraf-ng/iptraf-ng.mk b/package/iptraf-
> ng/iptraf-ng.mk
> index 7313873..404db8b 100644
> --- a/package/iptraf-ng/iptraf-ng.mk
> +++ b/package/iptraf-ng/iptraf-ng.mk
> @@ -11,5 +11,6 @@ IPTRAF_NG_LICENSE_FILES = LICENSE
> ?IPTRAF_NG_DEPENDENCIES = ncurses
> ?
> ?IPTRAF_NG_MAKE_ENV = NCURSES_LDFLAGS="-lpanel -lncurses"
> +IPTRAF_NG_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -D_GNU_SOURCE"
> ?
> ?$(eval $(autotools-package))

Any reason why this patch is marked as "Changes requested" in patchwork
[1]? The patch does fix the musl build issue, therefor:

Tested-by: J?rg Krause <joerg.krause@embedded.rocks>

[1]?http://patchwork.ozlabs.org/patch/572189/

      reply	other threads:[~2016-03-30 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 22:03 [Buildroot] [PATCH 1/1] package/iptraf-ng: Fix musl build Bernd Kuhls
2016-03-30 20:44 ` Jörg Krause [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=1459370663.1257.3.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.