From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux-pam: uses fork() needs MMU
Date: Thu, 18 Aug 2016 10:21:06 +0200 [thread overview]
Message-ID: <87vayypjwt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160818064956.jf7gt374yeehslfi@tarshish> (Baruch Siach's message of "Thu, 18 Aug 2016 09:49:56 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi Waldemar,
> On Thu, Aug 18, 2016 at 08:23:45AM +0200, Waldemar Brodkorb wrote:
>> Fixes:
>> http://autobuild.buildroot.net/results/8c9/8c9a5fe52f762b4ff4444cf41efdf0d3cf203986/
>>
>> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> [...]
>> diff --git a/package/util-linux/Config.in b/package/util-linux/Config.in
>> index 429dfa7..657bcdd 100644
>> --- a/package/util-linux/Config.in
>> +++ b/package/util-linux/Config.in
>> @@ -63,6 +63,7 @@ config BR2_PACKAGE_UTIL_LINUX_CHFN_CHSH
>> depends on (BR2_ENABLE_LOCALE && BR2_USE_WCHAR) # linux-pam
>> depends on !BR2_STATIC_LIBS
>> depends on !BR2_TOOLCHAIN_USES_MUSL # linux-pam
>> + depends on BR2_USE_MMU # linux-pam
>> select BR2_PACKAGE_LINUX_PAM
>> help
>> Change login shell, real user name and information
> Lots of packages select BR2_PACKAGE_UTIL_LINUX. All of them (and all packages
> that select them) now need to depend on BR2_USE_MMU.
Notice that this is only for BR2_PACKAGE_UTIL_LINUX_LOGIN_UTILS /
BR2_PACKAGE_UTIL_LINUX_CHFN_CHSH (which nothing selects), not the
toplevel util-linux option.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-08-18 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 6:23 [Buildroot] [PATCH] linux-pam: uses fork() needs MMU Waldemar Brodkorb
2016-08-18 6:49 ` Baruch Siach
2016-08-18 8:21 ` Peter Korsgaard [this message]
2016-08-18 8:59 ` Baruch Siach
2016-08-19 10:22 ` Thomas Petazzoni
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=87vayypjwt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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