From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem compiling busybox with libpam
Date: Wed, 26 Jan 2011 14:10:57 +0100 [thread overview]
Message-ID: <20110126141057.2be8a686@surf> (raw)
In-Reply-To: <87bp33vqwv.fsf@macbook.be.48ers.dk>
On Wed, 26 Jan 2011 12:35:28 +0100
Peter Korsgaard <jacmet@sunsite.dk> wrote:
> There's no pam support in uClibc/buildroot, so this can only work if you
> use an external glibc toolchain with pam support.
Hum, I'm not familiar at all with PAM, but it looks like it's a separate
library from the C library. At least on Debian systems,
security/pam_*.h are coming from libpam0g-dev, and the library is in
libpam0g, both of which are coming from the Linux-PAM project it seems.
How does it relate to the choosen C library ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-01-26 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=SoMmj4_=FMZnJ3cYTyJcTj2ymizEOM9PGSO3r@mail.gmail.com>
2011-01-26 2:09 ` [Buildroot] Problem compiling busybox with libpam Spider
2011-01-26 7:39 ` Thomas Petazzoni
2011-01-26 11:35 ` Peter Korsgaard
2011-01-26 13:10 ` Thomas Petazzoni [this message]
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=20110126141057.2be8a686@surf \
--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