[Rivet] AGILe does not configure

[Andy Buckley]

Holger Schulz wrote:
> Holger Schulz wrote:
>> Hi,
>>
>> having updated to the head version of AGILe,
>> I get the following complaints when running autoreconf -iv:
>>
>>    configure.ac:42: error: possibly undefined macro: AC_DISABLE_STATIC
>>          If this token and others are legitimate, please use
>>    m4_pattern_allow.
>>          See the Autoconf documentation.
>>    configure.ac:51: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
>>    configure.ac:52: error: possibly undefined macro: AC_PROG_LIBTOOL
>>    autoreconf: /users/eeh/hschulz/Software/bin/autoconf failed with
>>    exit status: 1
>>
>> I am using autoconf 2.64
>>
>> Any ideas what may have gone wrong?
>>
>> Holger
>>
> Maybe this is because I had to install autoconf 2.64 myself and some paths
> whatsoever are now not in standard locations. When I run automake I get:
> 
>     automake --add-missing --copy --no-force
>     src/AlpGen/Makefile.am:1: Libtool library used but `LIBTOOL' is
>     undefined
>     src/AlpGen/Makefile.am:1:   The usual way to define `LIBTOOL' is to
>     add `AC_PROG_LIBTOOL'
>     src/AlpGen/Makefile.am:1:   to `configure.ac' and run `aclocal' and
>     `autoconf' again.
>     src/AlpGen/Makefile.am:1:   If `AC_PROG_LIBTOOL' is in
>     `configure.ac', make sure
>     src/AlpGen/Makefile.am:1:   its definition is in aclocal's search path.
>     ...
> 
> Well, `AC_PROG_LIBTOOL' is in `configure.ac' but where can I find it's 
> definition and
> how do I tell aclocal where to search for it?

autoconf does seem to try to do some path guessing when you install it 
yourself, and most of the time it seems to cause more trouble than help.

Try using an autoreconf command like this:

LIBTOOL=/my/path/to/libtool AUTOCONF=/my/path/to/autoconf 
AUTOMAKE=/my/path/to/automake ACLOCAL=/my/path/to/aclocal autoreconf -i

It's worked for me before, and after the first time the paths seem to be 
remembered properly. However, post-installation and after a terminal 
restart, the autotools versions in your PATH seem to be used as 
expected... I never quite understood what was going on!

I also recommend installing a 2.2.x version of libtool, if you're 
already installing your own autoconf: it's nicer and plays better with 
some compilers... certainly on the Fortran side, but there may also be 
some improvements for C++.

Andy

-- 
Dr Andy Buckley
Particle Physics Experiment Group, University of Edinburgh