From: "Stefan Fröberg" <stefan.froberg@petroprogram.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 13:51:00 +0200 [thread overview]
Message-ID: <50A8CBA4.903@petroprogram.com> (raw)
In-Reply-To: <CANxTyt6cjey_R_w+ZupOqUF_oaN09eF5jUDt=TWu6fUSNT8SWA@mail.gmail.com>
Hi Danomi
18.11.2012 4:14, Danomi Manchego kirjoitti:
>
>
>
> On Sat, Nov 17, 2012 at 7:15 PM, Stefan Fr?berg
> <stefan.froberg@petroprogram.com
> <mailto:stefan.froberg@petroprogram.com>> wrote:
>
> +ifeq ($(shell sed -n "s/CONFIG_LOGIN=\(y\)/\1/p"
> $(BR2_PACKAGE_BUSYBOX_CONFIG)),y)
> +BUSYBOX_DEPENDENCIES += linux-pam
> +endif
>
>
> Why bother with the sed? Could you not do "ifeq
> ($(BR2_PACKAGE_LINUX_PAM),y)"?
>
No because I don't have a need for full linux-pam login binary.
I only need linux-pam because I have login applet enabled inside my
custom BusyBox .config file
and that needs Linux Pam headers.
Regards
Stefan
> Just a thought ...
> Danomi -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121118/e444326d/attachment.html>
next prev parent reply other threads:[~2012-11-18 11:51 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 [this message]
2012-11-18 12:11 ` Stefan Fröberg
2012-11-18 14:01 ` Stefan Fröberg
2012-11-18 16:40 ` Thomas Petazzoni
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=50A8CBA4.903@petroprogram.com \
--to=stefan.froberg@petroprogram.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