Unexpected automake version dependency causes build to fail

[Michael Abbott]

On Tue, 16 Dec 2008, Yann E. MORIN wrote:
> > It looks as if crosstool-ng-1.3.1 (or maybe the particular component 
> > I'm trying to build) has a fresh dependency on automake 1.10.1.
> You have to provide those. Exporting PATH with the correct order should 
> be enough to make those accessible.

Alas.  There seems to be more to this than immediately meets the eye (I've 
also seen this problem with automake elsewhere).

I've built m4, autoconf and automake (each in turn was insisted on by the 
following), installed them locally and placed the local installation dir 
on the path ... but I get the following mpfr build error:

[EXTRA]    Extracting and patching 'mpfr-2.3.2'
[ERROR]    configure.in:286: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
[ERROR]    configure.in:316: error: possibly undefined macro: AC_PROG_LIBTOOL
[ERROR]    Build failed in step 'Extracting and patching toolchain components'

and here's the appropriate part of build.log:

[ALL  ]    mpfr-2.3.2/sub1sp.c
[ALL  ]    Overiding config.guess and config.sub
[ALL  ]    `/scratch/tmp/crosstool-ng/src/crosstool-ng-1.3.1/tools/config.guess' -> `./config.guess'
[ALL  ]    `/scratch/tmp/crosstool-ng/src/crosstool-ng-1.3.1/tools/config.sub' -> `./config.sub'
[DEBUG]    Re-building autotools files
[DEBUG]    ==> Executing: 'autoreconf -fi'
[ERROR]    configure.in:286: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
[ALL  ]          If this token and others are legitimate, please use m4_pattern_allow.
[ALL  ]          See the Autoconf documentation.
[ERROR]    configure.in:316: error: possibly undefined macro: AC_PROG_LIBTOOL
[ALL  ]    autoreconf: /scratch/tmp/crosstool-ng/local/bin/autoconf failed with exit status: 1
[ERROR]    Build failed in step 'Extracting and patching toolchain components'

I guess there's some extra configuration information that automake needs?


Here's how I built things.  Set PATH=$LOCAL_ROOT/bin:$PATH (as it were), 
extracted m4 1.4.12, autoconf 2.63 and automake 1.10.2 (actually have 
installed m4 1.4.1, autoconf 2.59 and automake 1.9.2) and in each 
directory in turn ran
	./configure --prefix=$LOCAL_ROOT  &&  make install
Finally ran `./ct-ng build` with the same PATH.

Indeed, if I simply cd to mpfr-2.3.2 and run `autoreconf -fi` I get the 
same error message.

I *think* autoconf is ok.  My best guess is that the path to 
$LOCAL_ROOT/share isn't being inferred from the path to bin, and it's 
picking up the wrong files from my root installation instead...  I suspect 
it's actually automake that's failing.

--
For unsubscribe information see http://sourceware.org/lists.html#faq