Bug 466242 - Add configure option --disable-prelude
Add configure option --disable-prelude
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Fedora Extras Quality Assurance
: EasyFix
Depends On:
  Show dependency treegraph
Reported: 2008-10-09 07:54 EDT by Oliver Falk
Modified: 2009-03-09 11:44 EDT (History)
2 users (show)

See Also:
Fixed In Version: pam-1.0.90-4.fc11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-09 11:44:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Oliver Falk 2008-10-09 07:54:04 EDT
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
+ 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)...

Note You need to log in before you can comment on or make changes to this bug.