From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] coreutils: disable stdbuf for static builds
Date: Thu, 17 Dec 2015 22:48:26 +0100 [thread overview]
Message-ID: <20151217224826.62b06019@free-electrons.com> (raw)
In-Reply-To: <1448745450-19283-1-git-send-email-0intro@gmail.com>
Dear David du Colombier,
On Sat, 28 Nov 2015 22:17:30 +0100, David du Colombier wrote:
> When stdbuf is enabled, it builds a shared library,
> but it will fail in a static-only scenario.
>
> Signed-off-by: David du Colombier <0intro@gmail.com>
> ---
> package/coreutils/coreutils.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied, thanks. I've added a reference to the autobuilder failure that
this patch is fixing.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-17 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 21:17 [Buildroot] [PATCH 1/1] coreutils: disable stdbuf for static builds David du Colombier
2015-12-17 21:48 ` 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=20151217224826.62b06019@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