Bug 124206 - pam 0.77-40 does not build package
pam 0.77-40 does not build package
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2004-05-24 14:01 EDT by Steve Grubb
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-27 12:22:23 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 Steve Grubb 2004-05-24 14:01:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.4.2)

Description of problem:
Pam does not finish compiling from the src rpm for several reasons.

1) The dependancies are bad
2) The dlopen script is fatally flawed.


1) Pam 0.77-40 needs glib2-devel rather than glib-devel. Actually, the
correct dependencies are this:

Requires: cracklib, cracklib-dicts, glib, initscripts >= 3.94
Obsoletes: pamconfig
Prereq: grep, mktemp, sed, coreutils, /sbin/ldconfig
Requires: glib2, cracklib, cracklib-dicts
BuildPrereq: autoconf, bison, flex, glib2-devel, sed, cracklib,
BuildPrereq: perl, pkgconfig
Requires: libselinux
BuildPrereq: libselinux-devel

2) The dlopen script does not allow for the Library path of the new
shared object files to be passed in. It uses the normal system path
which definitely does not have the newly built libraries in it. The
pam spec file should be updated to pass their location like this:

# Check for module problems.  Specifically, check that every module we
# installed can actually be loaded by a minimal PAM-aware application.
for module in $RPM_BUILD_ROOT/%{_lib}/security/pam*.so ; do
        if ! $RPM_SOURCE_DIR/dlopen.sh -L$RPM_BUILD_ROOT/%{_lib} -lpam
-ldl ${module} ; then
                exit 1

Then dlopen needs to accept the -L argument like this @ line 43:

                ldflags="$ldflags $arg"

I honestly have no idea how you guys get this package compiled without
the above changes. It simply doesn't work as is.

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

How reproducible:

Steps to Reproduce:
1. rpmbuild -bb /usr/src/redhat/SPEC/pam.spec

Actual Results:  You get a message saying the build failed.

Expected Results:  A message saying where the newly built rpm is located.

Additional info:
Comment 1 Alan Cox 2004-07-27 12:22:23 EDT

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