Bug 31892 – sys-devel/automake-1.7.5-r2 does not use correct autoconf version.

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description klavs klavsen 2003-10-24 01:35:25 UTC]

output from emerging:

eutils
>>> Unpacking source...
>>> Unpacking automake-1.7.5.tar.bz2 to /var/tmp/portage/automake-1.7.5-r2/work
>>> Unpacking automake-1.6.3.tar.bz2 to /var/tmp/portage/automake-1.7.5-r2/work
>>> Unpacking automake-1.5.tar.gz to /var/tmp/portage/automake-1.7.5-r2/work
>>> Unpacking automake-1.4-p6.tar.gz to /var/tmp/portage/automake-1.7.5-r2/work
 * Applying automake-1.5-target_hook.patch...                                  
                                            [ ok ]
 * Applying automake-1.7.5-infopage-namechange.patch...                        
                                            [ ok ]
>>> Source unpacked.
eutils
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for perl... /usr/bin/perl
checking for tex... tex
configure: error: Autoconf 2.54 or better is required.
  Is it installed?  Is it in your PATH?  (try running `autoconf --version')
  Is it working?  See also config.log for error messages before this one.

!!! ERROR: sys-devel/automake-1.7.5-r2 failed.
!!! Function src_compile, Line 102, Exitcode 1
!!! (no error message)

I even tried to export the WANT_AUTOCONF_2_5=1 myself - so it worked in the
bash, where I started emerge - but no diff. I can see in the ebuild that the var
is actually exported, but for some reason it doesn't work - and I can't figure
out why.

Reproducible: Always
Steps to Reproduce:
1.emerge sys-devel/automake-1.7.5-r2
2.watch it bork..

[Comment 1 Caleb Tennis (RETIRED) 2003-10-24 06:33:14 UTC]

can you take a look in the config.log and see exactly what it's doing when
it determines that you don't have the right version.  maybe it's segfaulting.

[Comment 2 Martin Schlemmer (RETIRED) 2003-11-01 14:35:47 UTC]

Also, is this an existing system, or a new install ?

[Comment 3 Matthew Lowrance 2003-12-03 09:55:28 UTC]

I am having this same problem now as well and since the original poster seems to have disappeared, I'd like to help out to see if this one can get fixed.

To answer the second question, it has happened to me on an existing system.  I am trying to install a newer version of autoconf but it no matter what autoconf --version returns 2.13 and then automake fails with the same error.  

The ebuild of autoconf finishes correctly (as far as I can tell) but then it still always says version 2.13.  I have used the WANT_AUTOCONF_VERSION, and emerge says it installs version 2.58, and emerge unmerge autoconf says its unmerging 2.58.

I will attach config.log when I get home this evening, I don't currently have access to the file.

Thanks for any help with this.

[Comment 4 klavs klavsen 2003-12-03 12:21:35 UTC]

Yeah, sorry. The problem has gone away here - but I can't remember what I did to make it so. I've been so busy, so I've totally forgotten about this issue - and now it's not there anymore. Don't even remember on which machine the problem was :(

[Comment 5 Matthew Lowrance 2003-12-04 06:34:00 UTC]

Created attachment 21690 [details]
config.log

Here's the config.log for automake.

I don't see any error except that it can't find tex.

Is this the problem?

[Comment 6 Matthew Lowrance 2003-12-05 07:27:48 UTC]

I got this working finally, I don't think there was every really a problem, just alot of bad timing with enviroment variables in the wrong place at the wrong time.  

I think this is probably fixed and can be closed.  As long as the WANT_AUTOMAKE=2.5 has been issued, autoconf compiles without a problem.  Just wanted to update everyone.

[Comment 7 Caleb Tennis (RETIRED) 2004-01-04 10:06:41 UTC]

closing per comments by reporter.