The ebuild said "ERROR: module have dependencies in /usr. I checked this and the problem was, that ldd cracklib.so gave "/usr/lib/libcrack.so" instead of "/lib/libcrack.so". But there was libcrack.so in /lib. The dirty solution was to put "/lib" befor "/usr/lib" in "/etc/ld.conf" and do "ldconfig". I don't know how, but the ebuild should check, if there is REALLY a problem before it stops merging. Reproducible: Always Steps to Reproduce: 1. put "/usr/lib" before "/lib" in "/etc/ld.conf" 2. do "ldconfig" 3. try to emerge pam Actual Results: pam ebuild sais: "ERROR: module have dependencies in /usr" Expected Results: continue working... I don't think that you can assume that ldd or whatever the ebuild uses give the /lib/* version of every installed lib if there are more versions, so the error bothers needless.
thanks :-)
This was due to stale cracklib .so's in /usr/lib. Please just remove all libcrack.so.* in /usr/lib, and verify that you only have: -------------- libcrack.a libcrack.la libcrack.so <--- linker script, so wont influence ldd ... -------------- If you are NOT using cracklib-2.8 or later, please reopen and please add what pam and cracklib versions you are using, and the build failure, with a ldd of the module in ${D}/lib/security (ask if you are not sure).
