This is what an 'emerge -u pam' ends with: gcc -o pwdb_chkpwd pwdb_chkpwd.o md5_good.o md5_broken.o md5_crypt_good.o md5_crypt_broken.o -lpwdb pwdb_chkpwd.o: In function `bigcrypt': pwdb_chkpwd.o(.text+0x198): undefined reference to `crypt' pwdb_chkpwd.o(.text+0x1d0): undefined reference to `crypt' collect2: ld returned 1 exit status make[2]: *** [pwdb_chkpwd] Error 1 I'll be happy to give more details if needed (clue required though :).
Check if you have a /usr/lib/libcrypt.so symlink.
This is what I have: fallawater root # ls -l /usr/lib/libcrypt* -rw-r--r-- 1 root root 25410 Dec 9 03:36 /usr/lib/libcrypt.a -rw-r--r-- 1 root root 1536620 Nov 13 17:54 /usr/lib/libcrypto.a lrwxrwxrwx 1 root root 14 Nov 13 17:54 /usr/lib/libcrypto.so -> libcrypto.so.0 lrwxrwxrwx 1 root root 18 Nov 13 17:54 /usr/lib/libcrypto.so.0 -> libcrypto.so.0.9.6 -r-xr-xr-x 1 root root 998960 Nov 13 17:54 /usr/lib/libcrypto.so.0.9.6 fallawater root # qpkg -f /usr/lib/libcrypt.so sys-libs/glibc * So I remerged sys-libs/glibc-2.2.5-r7, but it didn't (re)create the link.
workshop gawk # ls -l /usr/lib/libcrypt.so lrwxrwxrwx 1 root root 23 Nov 4 10:45 /usr/lib/libcrypt.so -> ../../lib/libcrypt.so.1 workshop gawk # ----------------------------- What I have, so try to add back with: # ln -s ../../lib/libcrypt.so.1 /usr/lib/libcrypt.so Make sure its valid symlink, and then pam *should* merge fine. I will look into fixing glibc with linker scripts rather than symlinks ....
That made no difference...
Gerk, this seems to be similar to bug #4411 due to missing /usr/lib symlink, but aparently adding do not fix. Know of any PPC issues that could cause this as well ?
Hmm not sure Azarah my setup is the same as yours (has the symlink) gerk@ppc gerk $ ls -la /usr/lib/libcrypt.so lrwxrwxrwx 1 root root 23 Dec 2 13:16 /usr/lib/libcrypt.so -> ../../lib/libcrypt.so.1 BUT I am using: qpkg -f -v "/usr/lib/libcrypt.so" sys-libs/glibc-2.3.1-r2 * I've heard 2 complaints of this happening before (including this one) but havent been able to recreate it yet. cDlm: when was latest rsync update, etc... you sure you ahve the latest glibc? There was one patches one that was in the wild for about a week for ppc users that had some issues, has been fixed since then as a last resort you can try udating to glibc-2.3.1 and see if it helps you, its running very solid on my box and will in fact get upgraded to stable anytime on ppc :)
this should have gone to Azzie and i definately should have been added as a CC :P
cDlm: Can you try Gerk's advice ?
Hi, any feedback ?
Reopen if still issues.
