From: Alexandre Oliva <aoliva@redhat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
newlib@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
Date: Sat, 07 Dec 2002 12:55:00 -0000 [thread overview]
Message-ID: <ork7ily2oj.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <87adjk83ce.fsf@egil.codesourcery.com>
On Dec 5, 2002, Zack Weinberg <zack@codesourcery.com> wrote:
> AC_NO_EXECUTABLES has two effects: (1) it disables the equivalent of
> AC_PROG_CC_WORKS, which is what we need. But, (2) it causes autoconf
> to barf if an AC_TRY_LINK test appears anywhere in the script being
> generated.
Please tell me why (2) doesn't make sense.
If AC_PROG_CC_WORKS can't even link a do-nothing program, how would
you expect to get any useful results from AC_TRY_LINK?
> libstdc++-v3/configure.in has lots of AC_TRY_LINK tests.
If we know AC_PROG_CC_WORKS fails, it is a mistake to use AC_TRY_LINK
tests. Removing the constraint from autoconf will do us no good.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-12-07 20:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 14:36 Nathanael Nerode
2002-12-05 15:19 ` Zack Weinberg
2002-12-06 9:33 ` Tom Tromey
2002-12-07 12:55 ` Alexandre Oliva [this message]
2002-12-07 13:19 ` Zack Weinberg
2002-12-09 18:57 ` Alexandre Oliva
2002-12-09 21:52 ` Geoff Keating
2002-12-09 22:10 ` AC_NO_EXECUTABLES is useless for GCC Alexandre Oliva
2002-12-09 22:27 ` Ian Lance Taylor
2002-12-08 13:48 ` [RFC] Update to current automake/autoconf/libtool versions Tom Tromey
[not found] <9A4230D6-1D26-11D7-BFCA-00039396EEB8@apple.com>
2003-01-12 20:20 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 10:39 Nathanael Nerode
[not found] <20021206005522.GA11907@doctormoo>
[not found] ` <87of7sa16x.fsf@egil.codesourcery.com>
2002-12-12 13:29 ` Nathanael Nerode
2002-12-13 5:31 ` Alexandre Oliva
2002-12-10 19:33 Henry Nelson
2002-12-05 14:40 Joern Rennecke
2002-12-05 11:08 Nathanael Nerode
2002-12-05 11:31 ` Andrew Cagney
2002-12-05 13:31 ` Zack Weinberg
2002-12-05 14:29 ` Alan Modra
2002-12-05 15:14 ` Ian Lance Taylor
2002-12-05 15:32 ` Alan Modra
2002-12-05 15:45 ` Ian Lance Taylor
2002-12-05 16:26 ` Andrew Cagney
2002-12-05 15:47 ` Mike Stump
2002-12-05 16:30 ` Alan Modra
2002-12-05 16:36 ` Zack Weinberg
2002-12-08 2:48 ` Klee Dienes
2002-12-05 14:07 ` Christopher Faylor
2002-12-06 7:25 ` Maciej W. Rozycki
2002-12-08 3:23 ` Klee Dienes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ork7ily2oj.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=newlib@sources.redhat.com \
--cc=zack@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).