From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem compiling busybox with libpam
Date: Wed, 26 Jan 2011 08:39:05 +0100 [thread overview]
Message-ID: <20110126083905.0b0dab48@surf> (raw)
In-Reply-To: <AANLkTin4zfThtsb=2TobEPZWupSJAPmw1Xde2=OMiPER@mail.gmail.com>
Hello Spider,
On Wed, 26 Jan 2011 00:09:13 -0200
Spider <spiderwebmail@gmail.com> wrote:
> I was using buildroot to compile busybox and got the following error
> when I add libpam using "make busybox-menuconfig". ?(The output is
> below).
> How can I get libpam to compile without this errors? If I "make clean"
> and remake everything from scratch will it work? (I wil try this
> tomorrow because of the time to compile and fear of configuration files changes)
>
> I searched for a similar problem but didnt find anything on
> documentation. Do I need to manually supply security/pam_appl.h and
> security/pam_misc.h? Where to find them?
It looks like Busybox PAM support depends on the PAM library, for which
we don't have a package yet.
So you would need to :
* Create a Buildroot package for
ftp://ftp.kernel.org/pub/linux/libs/pam/library/Linux-PAM-1.1.3.tar.bz2
* Create a sub-option in the Busybox Buildroot package to
enable/disable PAM support. This option should select the PAM
library package created at the previous step.
* In package/busybox/busybox.mk, if PAM support is enabled, then tweak
the Busybox configuration file, and add the dependencies on the PAM
library.
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:[~2011-01-26 7:39 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 [this message]
2011-01-26 11:35 ` Peter Korsgaard
2011-01-26 13:10 ` 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=20110126083905.0b0dab48@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