From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: needs linux-pam dependency added if using custom busybox .config & busybox login applet
Date: Sun, 18 Nov 2012 17:40:00 +0100 [thread overview]
Message-ID: <20121118174000.0fe79ef6@skate> (raw)
In-Reply-To: <1353197713-20796-1-git-send-email-stefan.froberg@petroprogram.com>
Dear Stefan Fr?berg,
On Sun, 18 Nov 2012 02:15:13 +0200, Stefan Fr?berg wrote:
> +# linux-pam must be built first if user has custom
> +# BusyBox .config file and that file has also login
> +# applet (CONFIG_LOGIN) enabled.
> +ifeq ($(shell sed -n "s/CONFIG_LOGIN=\(y\)/\1/p" $(BR2_PACKAGE_BUSYBOX_CONFIG)),y)
> +BUSYBOX_DEPENDENCIES += linux-pam
> +endif
I don't think this will work nicely. BR2_PACKAGE_BUSYBOX_CONFIG is the
source for the Busybox configuration, but the user can do "make
busybox-menuconfig" do adjust it. In this case, the contents of the
BR2_PACKAGE_BUSYBOX_CONFIG file and the contents of the real
configuration file used by Busybox are different. If the latter has
CONFIG_LOGIN, but not the former, then you will not link against
linux-pam while you should.
It is really difficult to have dependencies that are needed only when
some specific Busybox features are enabled.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-18 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 0:15 [Buildroot] [PATCH] busybox: needs linux-pam dependency added if using custom busybox .config & busybox login applet Stefan Fröberg
2012-11-18 2:14 ` Danomi Manchego
2012-11-18 11:51 ` Stefan Fröberg
2012-11-18 12:11 ` Stefan Fröberg
2012-11-18 14:01 ` Stefan Fröberg
2012-11-18 16:40 ` Thomas Petazzoni [this message]
2012-11-18 17:39 ` Stefan Fröberg
2012-11-18 17:48 ` Thomas Petazzoni
2012-11-18 18:09 ` Stefan Fröberg
2012-11-18 18:28 ` 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=20121118174000.0fe79ef6@skate \
--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