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: Mon, 09 Dec 2002 19:16:00 -0000 [thread overview]
Message-ID: <ork7iiy43d.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <874r9pleth.fsf@egil.codesourcery.com>
On Dec 7, 2002, Zack Weinberg <zack@codesourcery.com> wrote:
> Alexandre Oliva <aoliva@redhat.com> writes:
>> 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?
> Because libstdc++'s AC_TRY_LINK tests are only executed in a situation
> where AC_PROG_CC_WORKS would have succeeded (i.e. a native compilation).
I don't get it. Why does being able to link have anything to do with
being native? Being able to *run* tests has to do with being native,
but that's not the point, and autoconf already avoids running tests
when cross-building. But being able to link has to do with whether
the libraries that the compiler links in by default are present or
not. That's the purpose of AC_NO_EXECUTABLES: to disable link tests
while building a library that the compiler driver would attempt to link
in by default, such as newlib, libstdc++ or libgcj.
That said, I'm not sure it should be used for libstdc++, since there's
no reason to use g++: we should use gcc instead, even if we perform
C++ link tests. Ditto for libjava, I suppose, but I realize it would
be far trickier to get libjava to link C programs :-)
Still, I think AC_NO_EXECUTABLES may affect all linking whatsoever,
not only that of the language in effect at the point it appears, which
does indeed make it useless for anything other that newlib. But, for
newlib, preventing link tests *is* the right thing to do, and I
contend that it's the right thing to do for any language affected by
the AC_NO_EXECUTABLES declaration.
--
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-10 2:56 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 14:40 Nathanael Nerode
2002-12-05 15:19 ` Zack Weinberg
2002-12-06 10:21 ` Tom Tromey
2002-12-07 13:06 ` Alexandre Oliva
2002-12-07 16:03 ` Zack Weinberg
2002-12-09 19:16 ` Alexandre Oliva [this message]
2002-12-09 21:52 ` Geoff Keating
2002-12-09 22:05 ` AC_NO_EXECUTABLES is useless for GCC Alexandre Oliva
2002-12-10 1:01 ` Ian Lance Taylor
2002-12-08 13:11 ` [RFC] Update to current automake/autoconf/libtool versions Tom Tromey
[not found] <9A4230D6-1D26-11D7-BFCA-00039396EEB8@apple.com>
2003-01-12 13:22 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 5:28 Nathanael Nerode
2002-12-05 14:42 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:36 ` Alan Modra
2002-12-05 14:56 ` Ian Lance Taylor
2002-12-05 15:22 ` Alan Modra
2002-12-05 15:43 ` Ian Lance Taylor
2002-12-05 15:51 ` Andrew Cagney
2002-12-05 15:47 ` Mike Stump
2002-12-05 16:30 ` Alan Modra
2002-12-05 16:45 ` Zack Weinberg
2002-12-08 2:49 ` Klee Dienes
2002-12-05 14:29 ` Christopher Faylor
2002-12-06 6:45 ` Maciej W. Rozycki
2002-12-08 10:53 ` Klee Dienes
2002-12-05 10:15 Michael Elizabeth Chastain
2002-12-05 10:37 ` Klee Dienes
2002-11-13 10:32 [RFA/PATCH] Darwin fixes for ltconfig, ltcf-c.sh Klee Dienes
2002-12-04 22:04 ` [RFC] Update to current automake/autoconf/libtool versions Klee Dienes
2002-12-05 5:26 ` Hans-Peter Nilsson
2002-12-05 14:07 ` Alan Modra
2002-12-05 7:43 ` Andrew Cagney
2002-12-05 8:22 ` Klee Dienes
2002-12-05 9:01 ` Andrew Cagney
2002-12-05 12:55 ` Klee Dienes
2002-12-05 13:03 ` Daniel Jacobowitz
2002-12-05 13:13 ` Andrew Cagney
2002-12-05 13:16 ` Daniel Jacobowitz
2002-12-05 13:08 ` Andrew Cagney
2002-12-05 13:18 ` Klee Dienes
2002-12-05 8:28 ` DJ Delorie
2002-12-05 9:37 ` Klee Dienes
2002-12-05 9:42 ` DJ Delorie
2002-12-05 10:28 ` Klee Dienes
2002-12-05 9:31 ` H. J. Lu
2002-12-05 7:44 ` Maciej W. Rozycki
2002-12-05 9:01 ` Klee Dienes
2002-12-05 8:09 ` Daniel Jacobowitz
2002-12-05 8:29 ` DJ Delorie
2002-12-05 8:35 ` Daniel Jacobowitz
2002-12-05 8:37 ` DJ Delorie
2002-12-05 8:40 ` Maciej W. Rozycki
2002-12-05 8:44 ` Daniel Jacobowitz
2002-12-05 9:19 ` Elena Zannoni
2002-12-05 9:54 ` Klee Dienes
2002-12-05 10:10 ` Maciej W. Rozycki
2002-12-05 10:59 ` Andrew Cagney
2002-12-06 5:52 ` Maciej W. Rozycki
2002-12-05 10:59 ` Doug Evans
2002-12-05 12:11 ` Klee Dienes
2002-12-05 12:23 ` Ian Lance Taylor
2002-12-05 14:29 ` Klee Dienes
2002-12-06 5:34 ` Maciej W. Rozycki
2002-12-06 7:25 ` DJ Delorie
2002-12-06 8:06 ` Maciej W. Rozycki
2002-12-06 8:47 ` DJ Delorie
2002-12-05 13:59 ` Ben Elliston
2002-12-05 13:41 ` Ben Elliston
2002-12-30 16:10 ` Alexandre Oliva
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=ork7iiy43d.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