This is the mail archive of the
mailing list for the binutils project.
Re: [RFC] Update to current automake/autoconf/libtool versions.
- From: Tom Tromey <tromey at redhat dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Nathanael Nerode <neroden at twcny dot rr dot com>, gdb-patches at sources dot redhat dot com, binutils at sources dot redhat dot com, newlib at sources dot redhat dot com, gcc at gcc dot gnu dot org
- Date: 08 Dec 2002 12:58:17 -0700
- Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
- References: <20021205223538.GA24616@doctormoo><firstname.lastname@example.org><email@example.com>
- Reply-to: tromey at redhat dot com
>>>>> "Alexandre" == Alexandre Oliva <firstname.lastname@example.org> writes:
>> But, (2) it causes autoconf to barf if an AC_TRY_LINK test appears
>> anywhere in the script being generated.
Alexandre> Please tell me why (2) doesn't make sense.
Alexandre> If AC_PROG_CC_WORKS can't even link a do-nothing program,
Alexandre> how would you expect to get any useful results from
The autoconf code in question completely disables AC_LINK_IFELSE.
However, we know we can successfully do link tests when building
natively. And, at least in libgcj's case, this knowledge is important
because we use it to make libgcj more functional when built native.
FYI I sent a patch to the autoconf list.