4596 – autoconf 2.53 is actually 2.13?

Bug 4596 - autoconf 2.53 is actually 2.13?

Summary: autoconf 2.53 is actually 2.13?

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Development (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Martin Schlemmer (RETIRED)

URL:
Whiteboard:
Keywords:

Duplicates (1):	10400 (view as bug list)
Depends on:
Blocks:

Reported:	2002-07-05 15:58 UTC by Peter Bienstman (RETIRED)
Modified:	2002-11-07 17:50 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Peter Bienstman (RETIRED) gentoo-dev

2002-07-05 15:58:32 UTC

After emerging autoconf, 'emerge -s' claims I have version 2.53 installed, but 
'autoconf --version' tells me it's only 2.13. 
 
This breaks compiling cvs KDE apps, as make -f Makefile.cvs will fail

Comment 1 Martin Schlemmer (RETIRED) gentoo-dev

2002-07-07 02:40:08 UTC

Please check the ebuild.  As autoconf-2.53 is not 100% backwards compadible
with 2.13, it breaks many packages.  Thus we have a "dual" setup.

In a perfect world, KDE apps which uses autoconf-2.50 or later, should have
"AC_PREREQ[2.50]" in configure.in.  This will cause the autoconf wrapper
to switch to 2.53a.  If they do not (and are broken if you ask me), then
just do something like:

# WANT_AUTOCONF_2_5=1 ./configure && make

This will tell the wrapper to switch to 2.53a as well.

Comment 2 Martin Schlemmer (RETIRED) gentoo-dev

2002-11-07 17:50:35 UTC

*** Bug 10400 has been marked as a duplicate of this bug. ***