From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] util-linux: build schedutils without enabling basic binaries
Date: Mon, 20 Feb 2017 21:43:41 +0100 [thread overview]
Message-ID: <20170220214341.1155737d@free-electrons.com> (raw)
In-Reply-To: <1487610335-7149-1-git-send-email-casantos@datacom.ind.br>
Hello,
On Mon, 20 Feb 2017 14:05:35 -0300, Carlos Santos wrote:
> Pull an upstream fix to allow building schedutils (ionice, taskset,
> chrt) when util-linux is configured with
>
> $ configure --disable-all-programs --enable-schedutils
>
> Fixes:
> https://bugs.busybox.net/show_bug.cgi?id=9656
>
> Reported-by: Aaron Holtzman <aholtzma@gmail.com>
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> Changes v1->v2
> Update comment explaining why we need UTIL_LINUX_AUTORECONF = YES
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 20:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 17:58 [Buildroot] [Bug 9656] New: util-list: schedutils doesn't build on target w/o enabling basic binaries bugzilla at busybox.net
2017-02-13 4:21 ` [Buildroot] [Bug 9656] util-linux: " bugzilla at busybox.net
2017-02-18 20:06 ` [Buildroot] [PATCH] util-linux: build schedutils without " Carlos Santos
2017-02-18 20:26 ` Baruch Siach
2017-02-18 20:45 ` [Buildroot] [PATCH v2] " Carlos Santos
2017-02-20 17:05 ` [Buildroot] [PATCH v3] " Carlos Santos
2017-02-20 20:43 ` Thomas Petazzoni [this message]
2017-02-13 13:05 ` [Buildroot] [Bug 9656] util-linux: schedutils doesn't build on target w/o " bugzilla at busybox.net
2017-02-18 17:53 ` bugzilla at busybox.net
2017-02-18 20:11 ` bugzilla at busybox.net
2017-02-20 20:43 ` bugzilla at busybox.net
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=20170220214341.1155737d@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 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.