Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fixing linux-pam build failures
Date: Sat, 08 Sep 2012 14:28:19 +0300	[thread overview]
Message-ID: <504B2BD3.5080205@petroprogram.com> (raw)
In-Reply-To: <CADiAo4L2eUCF-2dEBWEJbw1V9z7uaQ-1=AA6z9SE4FA9v529+Q@mail.gmail.com>

Hi Dmitry!

Your work on this pam support looks good.

I have attached in this message my very quick, unpolished & very very
very dirty pam (version 1.1.5) hack
(it doesn't bother to even check for if pam is enabled in busybox and it
assumes that pam.d stuff is already in fs/skeleton/etc )

I can't even remember when I did this ugly hack.

Got it somehow working with the help of :
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/linux-pam.html
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/shadow.html
and
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/cracklib.html

Those Linux From Scratch pages are really great starting templates for
any new buildroot package!
:)

Also, those three patches mentioned in this attached file are from
openwrt project witch also
uses buildroot  stuff (???).

https://dev.openwrt.org/browser/packages/libs/libpam

If you find something usefull for your work then by all means salvage
what you need from it.

I just want to get quickly rid of my dirty pam hack as soon as official
support lands on buildroot.

Stefan

P.S:

Your work for v86d ( http://patchwork.ozlabs.org/patch/157286/ )
is working wonderfully in my distro !
Thanks!


8.9.2012 7:32, Dmitry Golubovsky kirjoitti:
> Hi,
>
> My initial assumption about the failures of linux-pam building in
> autobuilder was not correct: the problem was in BerkeleyDB
> configuration.
>
> When BerkeleyDB is not built, the pam_userdb module is not built
> either (via linux-pam configure). In this failed autobuilder
> configuration Berkeley DB was selected. But dbm functionality was not
> enabled in BerkeleyDB configure options. Thus the pam_userdb module
> was attempted to build, but it failed due to the absence of dbm
> functions in Berkeley DB, and this showed up in the build log.
>
> I have submitted a series of patches which address the problem:
>
> * if linux-pam is built, --enable-dbm is added to BerkeleyDB configure options
> * BerkeleyDB is autoselected when linux-pam is selected, and
> BerkeleyDB is now a dependency of linux-pam
>
> I also included my two other patches (since linux-pam is being patched anyway):
>
> * Provide dummy PAM config files to allow password-less logons via busybox login
> * New configuration option for PAM support has been added to the
> Busybox configuration menu.
>
> Any suggestions are welcome.
>
> Thanks.
>

-------------- next part --------------

  reply	other threads:[~2012-09-08 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  4:32 [Buildroot] Fixing linux-pam build failures Dmitry Golubovsky
2012-09-08 11:28 ` Stefan Fröberg [this message]
2012-09-08 12:54   ` Dmitry Golubovsky
2012-09-08 14:40     ` Stefan Fröberg

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=504B2BD3.5080205@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