http://qa.mandrakesoft.com/show_bug.cgi?id=6362
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|program |program
Product|autoconf2.5 |automake1.7
Version|2.57-4mdk |1.7.6-1mdk
------- Additional Comments From [EMAIL PROTECTED] 2003-11-15 01:57 -------
Might not actually be a bug. It's happening because I'm getting the 1.4
aclocal. In the past you could either have 1.7 or 1.4 installed but not both.
It's now using alternatives but 1.4 is the default. So now packages that
required 1.6 or 1.7 and assumed that they were getting it on the basis of the
package being installed need to also use the version specific path. I'm not
sure there's a fix except to write a wrapper that figures out which automake
version you really want. But I'm not sure there's a good way to do that. I'll
leave it as new in case someone wants to figure out a better way to deal with this.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
conifgure.ac's using the new style AC_INIT and AM_INIT_AUTOMAKE macros produce
wrong output.
A good example is ayttm or esmtp. To replicate get ayttm 0.4.4, run ./gen.
ayttm has:
AC_INIT(Ayttm, 0.4.4, [EMAIL PROTECTED])
AM_INIT_AUTOMAKE([1.6 dist-bzip2 dist-zip])
in its configure.ac.
Which produces the following output in the configure script:
PACKAGE=1.6 dist-bzip2 dist-zip
VERSION=
instead of:
PACKAGE=ayttm
VERSION=0.4.4
