Bug 428444 - requirement script doesn't report that pam needs libtool
requirement script doesn't report that pam needs libtool
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Tomas Mraz
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-11 11:04 EST by Josef Kubin
Modified: 2008-01-14 05:42 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-14 05:42:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josef Kubin 2008-01-11 11:04:35 EST
Description of problem:
$ cvs co pam
$ make sources
$ make prep
...
Patch #46 (pam-0.99.8.1-succif-in-operator.patch):
+ patch -p1 -b --suffix .in-operator -s
+ echo 'Patch #47 (pam-0.99.8.1-xauth-no-free.patch):'
Patch #47 (pam-0.99.8.1-xauth-no-free.patch):
+ patch -p1 -b --suffix .no-free -s
+ autoreconf
configure.in:58: error: possibly undefined macro: AC_ENABLE_STATIC
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:59: error: possibly undefined macro: AC_ENABLE_SHARED
configure.in:75: error: possibly undefined macro: AC_PROG_LIBTOOL
autoreconf: /usr/bin/autoconf failed with exit status: 1
error: Bad exit status from /var/tmp/rpm-tmp.60730 (%prep)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.60730 (%prep)
make: *** [prep] Error 1
$

Version-Release number of selected component (if applicable):
$ cat pam.spec
...
Name: pam
Version: 0.99.8.1
Release: 10%{?dist}
...
Comment 1 Tomas Mraz 2008-01-14 05:42:22 EST
The make prep command unfortunately doesn't evaluate BuildRequires. If you'd
built the rpm through rpmbuild -bb pam.spec you'd see that libtool is required.

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