This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 163502 - pam not self-hosting, links to already installed(older)
pam not self-hosting, links to already installed(older)
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Depends On:
  Show dependency treegraph
Reported: 2005-07-18 08:34 EDT by Karsten Hopp
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: pam-0.80-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-16 04:21:04 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 Karsten Hopp 2005-07-18 08:34:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.8) Gecko/20050623 Fedora/1.0.4-5 Firefox/1.0.4

Description of problem:
pam isn't self-hosting as it needs pam-devel to rebuild.
Otherwise a rebuild fails with

+ for module in '$RPM_BUILD_ROOT/lib/security/pam*.so'
+ /usr/src/redhat/SOURCES/ -lpam -ldl -L/var/tmp/pam-root/lib /var/tmp/pam-root/lib/security/
/usr/bin/ld: cannot find -lpam
collect2: ld returned 1 exit status
/usr/src/redhat/SOURCES/ line 63: /tmp/dlopeny29384/dlopen: No such file or directory

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpm -e pam-devel
2. rpmbuild --rebuild pam-0.80-1.src.rpm
3. check output

Actual Results:  pam builds a dlopen wrapper to check if the modules can be loaded. This wrapper should be linked with /var/tmp/pam-root/lib/ instead of /lib/

This is the obvious error, still need to check if the dlopen-wrapper is the only pam binary which links with older libpam outside of /var/tmp/pam-root/.

Additional info:
Comment 1 Tomas Mraz 2005-08-16 04:21:04 EDT
I've forgot to close the bug.

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