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 16:01:53 +0200 [thread overview]
Message-ID: <50A8EA51.1070505@petroprogram.com> (raw)
In-Reply-To: <50A8D08E.7060806@petroprogram.com>
18.11.2012 14:11, Stefan Fr?berg kirjoitti:
> 18.11.2012 13:51, Stefan Fr?berg kirjoitti:
>> 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.
>>
> Or to but it in another way:
>
> BR2_PACKAGE_LINUX_PAM is not enough. BusyBox .config must also have
> CONFIG_LOGIN enabled.
> And that needs to be determined before the whole .mk is parsed, at a
> runtime, so that proper
> dependency can be added.
>
> In normal default buildroot provided BusyBox .config there is no
> CONFIG_LOGIN enabled in.
> So for that case this will change nothing.
>
> It seems that the stuff inside .mk files are really static (and so
> called functions are not functions at all
> but just variables containing text).
>
> So I had to go outside of .mk file for a moment and determine if
> CONFIG_LOGIN was enabled outside of extracted
> busybox dir and then add the needed dependency.
>
> I know this is ugly but Im open to suggestions.
>
> Regards
> Stefan
>
Actually, maybe that should be changed to host-linux-pam ...
Because AFAIK, BusyBox login applet needs only headers and nothing more ???
>
>
>
>>
>> Regards
>> Stefan
>>
>>> Just a thought ...
>>> Danomi -
>>>
>>
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121118/1381142e/attachment.html>
next prev parent reply other threads:[~2012-11-18 14:01 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 [this message]
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=50A8EA51.1070505@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 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.