After successfully building the various modules something (ebuild?) emits this line and causes the emerge to fail: * ERROR: pam_pwdb module did not build. I'll attach the complete emerge session record for reference, otherwise paste it in as a comment. Note that I believe this is _not_ a duplicate of bug #9607 as I am not having the same glib library problem. 9607 never got to the point of trying to build pam_pwdb. The relevent part of the attachment will be, I believe this: make[2]: Entering directory `/var/tmp/portage/pam-0.75-r9/work/Linux-PAM-0.75/modules/pam_pwdb' This module will not be compiled on this system make[2]: Leaving directory `/var/tmp/portage/pam-0.75-r9/work/Linux-PAM-0.75/modules/pam_pwdb' What ever caused it to make this assessment is the problem. Unfortunately I don't know why it would do this right now.
Created attachment 5030 [details] Output captured from emerge --update world Output (stdout and stderr) captured from an emerge --update world executed after emerge rsync perormed 10/25/2002 around 00:00 GMT.
Created attachment 5031 [details] Output from qpkg -I -v Complete listing of packages installed on the system.
Created attachment 5032 [details] Output from qpkg -I -nc -v Textual version of qpkg output. Obsoletes 5031...
update to sys-libs/pwdb-0.61-r4 and remerge pam (btw, -r10 is out ...). *** This bug has been marked as a duplicate of 4411 ***