[Rivet] AGILe does not configure (sort of SOLVED, but gcc4-1 -pedantic problem)

Holger Schulz holger.schulz at physik.hu-berlin.de
Thu Oct 22 17:23:12 BST 2009


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?
>
> Holger
>
>
>
>
Hi again,

I have found a libtool.m4 file in the garbage collector package that
I copied to agiles m4 folder and now it works again. However, building
Rivet fails probably due to our old gcc-4.1 compiler with the error
message

    error: ISO C++ does not support 'long long'

Google tells me that this is due to the compiler flag -pedantic and
indeed removing this flag from the g++ command does the trick.
However, I have not been able to run configure in such a way, that
the pedantic flag vanishes from all the commands. How do I do
that?

Cheers,
Holger



More information about the Rivet mailing list