Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 2962 - autoconf has an undefined macro in it
autoconf has an undefined macro in it
Product: Red Hat Linux
Classification: Retired
Component: autoconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 1999-05-22 07:39 EDT by Kevin
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-09-05 16:03:32 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 Kevin 1999-05-22 07:39:38 EDT
this is an exact printout of the error message:
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_DISABLE_FAST_INSTALL
Comment 1 Jeff Johnson 1999-05-22 09:00:59 EDT
Please supply the name-version-release of autoconf that you are
using as well as sufficient context for us to reproduce this bug.
Comment 2 Kevin 1999-05-22 19:14:59 EDT
I believe it was autoconf 4.13-5, and this error occurred while I was
trying to compile gettext....brb with the exact version #'s.
Comment 3 kevmcc 1999-05-22 19:42:59 EDT
ok...the exact version #'s are as follows:
You can duplicate this error as follows
rpm -ba --clean --rmsource --sign --target i686-redhat-linux
This is the exact command I ran after I did an rpm -i -v
gettext-0.10.35-8.src.rpm and I was in my SPECS dir.
I have successfully installed and recompiled 99 % of my other packages
this same way (trying to optimize for i686..and yes...I edited my
/usr/lib/rpm/macros file and changed i386 to i686..some of the package
sources had to be edited, but I managed) didn't edit gettext though.
Comment 4 Jeff Johnson 1999-09-05 10:54:59 EDT
Your test case (w/o --sign) works with

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