Bug 89201 - krb5-1.2.8-1.src.rpm fails to compile with autoconf-2.57-3
krb5-1.2.8-1.src.rpm fails to compile with autoconf-2.57-3
Product: Red Hat Raw Hide
Classification: Retired
Component: krb5 (Show other bugs)
other Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-04-20 13:53 EDT by Felipe Alfaro Solana
Modified: 2007-04-18 12:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-26 07:18:50 EST
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 Felipe Alfaro Solana 2003-04-20 13:53:15 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
I'm unable to compile krb5-1.2.8.src.rpm if autoconf-2.57-3 (the one that comes
with Red Hat Linux 9) is installed. During the compilation process, the build
stops complaining that autoconf doesn't recognize the "--localdir" and
"--macrodir" arguments.

To fix the problem, I uninstalled autoconf-2.57-3 and installed
autoconf213-2.13-6 instead, and then made a symbolic link from
/usr/bin/autoconf-2.13 to /usr/bin/autoconf. This time, I was able to recompile
the SRPM successfully.

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

How reproducible:

Steps to Reproduce:
1. Download krb5-1.2.8-1.src from RawHide
2. Make sure autocong-2.57-3 is installed
3. rpmbuild --rebuild krb5-1.2.8-1.src.rpm

Actual Results:  Building of the source package fails complaining that autconf
doesn't support the "--localdir" or "--macrodir" command-line parameter.

Expected Results:  It should be possible to compile krb5-1.2.8-1.src.rpm using

Additional info:
Comment 1 Felipe Alfaro Solana 2004-02-26 07:18:50 EST
I'm closing this pretty old bug as current Kerberos V packages are 
at upstream release 1.3. 
If anyone is still experiencing this, please consider upgrading to 
latest Kerberos V packages and open a new bug is this problem 

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