Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 69761 - PAM 0.77 Compilation error at pam_cracklib.so - /usr/lib/libcrack.a not found!
Summary: PAM 0.77 Compilation error at pam_cracklib.so - /usr/lib/libcrack.a not found!
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: Lowest critical (vote)
Assignee: PAM Gentoo Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-01 13:03 UTC by Christoffer Aasted
Modified: 2004-11-08 02:26 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoffer Aasted 2004-11-01 13:03:57 UTC
I tried to compile both pam-0.77 from ARCH and pam-0.77-r2 from ~ARCH, both give this compilation error at pam_cracklib.so, this piece is just before the compilation crashes ..

*** Starts to compile the module
gcc -shared -L/var/tmp/portage/pam-0.77-r2/work/Linux-PAM-0.77/lib -o pam_cracklib.so dynamic/pam_cracklib.o //usr/lib/libcrack.a -lcrypt -lc -L../pammodutil -lpammodutil
*** Gives error
gcc: //usr/lib/libcrack.a: No such file or directory
make[2]: *** [pam_cracklib.so] Error 1
make[2]: Leaving directory `/var/tmp/portage/pam-0.77-r2/work/Linux-PAM-0.77/modules/pam_cracklib'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/var/tmp/portage/pam-0.77-r2/work/Linux-PAM-0.77/modules'
make: *** [modules] Error 2
*** Ends, telling me that i failed and if i need support i should post this messge.

Reproducible: Always
Steps to Reproduce:





I've just sync'ed, and just updated world, i got this error just after
uninstalling db, and then reinstalling pam.
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-11-02 01:38:06 UTC
what version of cracklib do you have presently?
if you sync and re-compile cracklib, does pam compile?
Comment 2 Christoffer Aasted 2004-11-02 08:55:41 UTC
# emerge sync && emerge --oneshot cracklib && emerge pam

That's what i did at first. Tried again, still doesn't work, and same error :( ..
Comment 3 Per Cederqvist 2004-11-07 11:51:13 UTC
I get the same problem. I'm trying to install Gentoo from stage 1 on a box.
While progressing from Stage2 to Stage3 I get this error.  sys-libs/cracklib-2.7-r9 is installed.  It has created the following files in /lib/ (not /usr/lib!):

/lib/libcrack.so  /lib/libcrack.so.2  /lib/libcrack.so.2.7

There is no libcrack.a anywhere on the system.  These three files are the only ones that match libcrack\* in the entire chrooted new Gentoo environment.

I have "-pam" in my USE flags.  I'm a little disappointed that pam-0.77 seems to be installing on my system.

I have tried to "emerge sync; emerge cracklib; emerge system" but I still get stuck at the same place.
Comment 4 Per Cederqvist 2004-11-07 13:37:03 UTC
Workaround: make sure that cracklib is merged with "pam" in the USE flags.  Then
you can merge pam and it will work, because libcrack.a will be installed by the
craclib ebuild when "pam" is defined.

Christoffer, have you also compiled cracklib with "-pam"?
Comment 5 Christoffer Aasted 2004-11-07 14:35:37 UTC
Per Cederqvist: Thank you so much :) .. It would help alot with a NOTE on this ebuild if someone could do that?
Comment 6 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-11-07 17:08:30 UTC
please try sys-libs/cracklib-2.7-r10 instead of r9, and report back if that solves the problem for you (it should I think).
Comment 7 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-11-07 17:09:10 UTC
don't close the bug until it's actually fixed. workarounds don't count.
Comment 8 Per Cederqvist 2004-11-08 02:22:50 UTC
sys-libs/cracklib-2.7-r10 solves the problem for me.  I am now able to compile
the pam module.  I have not tested the resulting files.
Comment 9 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-11-08 02:26:31 UTC
r10 moved to stable on x86 so that this is solved for everybody.