A few days ago Jay Estabrook reported to me, that he cannot recompile PAM, due to the following error:

env LD_LIBRARY_PATH=/var/tmp/pam-1.0.1-2.fc9-root-root/lib
LD_PRELOAD=/var/tmp/pam-1.0.1-2.fc9-root-root/usr/lib/libpam.so ldd -r
/var/tmp/pam-1.0.1-2.fc9-root-root/lib/security/pam_access.so
+ fgrep -q libpthread
+ echo ERROR module:
/var/tmp/pam-1.0.1-2.fc9-root-root/lib/security/pam_access.so pulls threading libraries.
ERROR module: /var/tmp/pam-1.0.1-2.fc9-root-root/lib/security/pam_access.so pulls threading libraries.
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.12271 (%check)

That's because he recompiled PAM on his system and not in a chroot environment and he has prelude installed. However, the problem should (untested!) avoided, when using --disable-prelude configure option.

While this might not be a *real* bug, it might become a problem, when something would pull in libprelude in the build-chroot (mock/koji)...