From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] add pam to busybox
Date: Thu, 1 Sep 2011 10:08:00 +0200 [thread overview]
Message-ID: <20110901100800.357eb581@skate> (raw)
In-Reply-To: <32325731.post@talk.nabble.com>
Hello,
Le Sun, 28 Aug 2011 22:34:09 -0700 (PDT),
brro1 <rotembr@gmail.com> a ?crit :
> hi all
> i tryed to add pam tp busybox.
> i make pam with build=i386-linux --host=arm-none-linux-gnueabi and enable
> pam at busybox config file
> when i build the busybox i see this error
>
> LINK busybox_unstripped
>
> Trying libraries: crypt m pam pam_misc
> Failed: -Wl,--start-group -lcrypt -lm -lpam -lpam_misc -Wl,--end-group
> .....
> skipping incompatible /Linux-PAM-0.80/libpam/libpam.a when searching for
> -lpam
> /CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/./../../../arm-none-linux-gnueabi/bin/ld:
> cannot find -lpam
> skipping incompatible /Linux-PAM-0.80/libpam/libpam.so when searching for
> -lpam
> /CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/./../../../arm-none-linux-gnueabi/bin/ld:
> cannot find -lpam
> collect2: ld returned 1 exit status
> make[1]: *** [busybox_unstripped] Error 1
> make[1]: Leaving directory
>
> how can i fixed this error?
I guess your pam is improperly configured, compiled or installed.
I would recommend to add the necessary pam packages to the Buildroot
packages and then make Busybox depend on it.
Regards,
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-09-01 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 5:34 [Buildroot] add pam to busybox brro1
2011-09-01 8:08 ` 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=20110901100800.357eb581@skate \
--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 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.