This is the mail archive of the
mailing list for the GCC project.
Re: tweaks for autoconf 2.50
- To: Geoff Keating <geoffk at redhat dot com>
- Subject: Re: tweaks for autoconf 2.50
- From: "Zack Weinberg" <zackw at Stanford dot EDU>
- Date: Fri, 25 May 2001 13:01:15 -0700
- Cc: gcc at gcc dot gnu dot org
On Fri, May 25, 2001 at 12:06:27PM -0700, Geoff Keating wrote:
> > Date: Fri, 25 May 2001 11:43:42 -0700
> > From: "Zack Weinberg" <zackw@Stanford.EDU>
> > Cc: email@example.com
> > On Fri, May 25, 2001 at 11:37:06AM -0700, Geoff Keating wrote:
> > I think you misunderstood. Any configure script that uses libtool's
> > autoconf macros will barf. F'r instance, libstdc++v3:
> > configure.in:50: error: All the tests involving linking were disabled by AC_NO_EXECUTABLES
> > acgeneral.m4:2882: AC_TRY_LINK is expanded from...
> > ../libtool.m4:208: AC_LIBTOOL_SETUP is expanded from...
> > configure.in:50: AC_LIBTOOL_SETUP is required by...
> > ../libtool.m4:86: _AC_PROG_LIBTOOL is expanded from...
> > configure.in:50: _AC_PROG_LIBTOOL is required by...
> > ../libtool.m4:52: AC_PROG_LIBTOOL is expanded from...
> > ../libtool.m4:839: AM_PROG_LIBTOOL is expanded from...
> > configure.in:50: the top level
> > Doesn't matter if it was otherwise cross-compiler clean.
> Hmmm. Sounds like libtool will need some fixing, then. It probably
> only works now by chance.
At the moment I'm inclined to punt and duplicate enough of the 2.13
machinery that LIB_AC_PROG_CC will continue to work, at least on the
branch. Unless Alexandre wants to come up with a miracle cure for
zw But then one day I came up with a radical new paradigm for my business...
I decided that from now on I would only sell boring stuff that people
-- Garry Trudeau, _Doonesbury_