From: Nathanael Nerode <neroden@twcny.rr.com>
To: aoliva@redhat.com
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Partial autoconf transition thoughts
Date: Tue, 10 Jun 2003 01:40:00 -0000 [thread overview]
Message-ID: <20030610014019.GA14933@doctormoo> (raw)
Alexandre said:
>I.e., assume you're always cross compiling? That would be a
Actually, assume you're always Canadian cross compiling. :-) Except
when you aren't.
>reasonable approach too, but there are some tests that you can't
>possibly do in the cross case, autoconf lets you actually do them in
>the native case as long as you set a safe default or alternate test
>for the cross case.
And when I write my own tests for these circumstances, I would guard
them by one of build=host or build=target, depending on which is correct
under the circumstances.
This generally tests in the correct situations, and is if anything too
conservative (assuming untestability when build=i686-pc-linux-gnu
and host=i386-pc-linux-gnu).
I suppose the idea behind the proposal is that you can always
force nativeness by not specifying 'host' (since it defaults to build);
but there's no clear way to force 'crossness' when host=build.
But why would you *want* to?
Perhaps you have two machines with the same canonical name, but
differing in the particular feature. This is most likely due to a bug
in config.guess or config.sub, which is Not Autoconf's Problem.
Otherwise, the feature is probably one where I don't *want* autoconf to
decide based on my particular build machine; it will presumably make
the produced program quite unportable, and will likely break if I make
some small change to my machine's configuration. Such a feature
probably deserves its own --with option and notes in the documentation,
and should certainly be defaulted to the 'baseline' option, not to
whatever's on my machine today.
So the only use case I can think of for 'forcing crossness' when
build=host depends on either bugs in config.* or poor 'configure'
design.
Hmm. Now who should I say this to?
Akim, I guess, but he still hasn't done anything with the autoconf patch
I sent him a long while ago.
--Nathanael
next reply other threads:[~2003-06-10 1:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 1:40 Nathanael Nerode [this message]
2003-06-10 1:46 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 0:40 Nathanael Nerode
2003-06-10 0:59 ` Alexandre Oliva
2003-06-10 10:59 ` Maciej W. Rozycki
2003-06-10 11:38 ` Andreas Schwab
2003-06-10 12:45 ` Maciej W. Rozycki
2003-06-10 22:06 ` Alexandre Oliva
2003-06-11 11:32 ` Maciej W. Rozycki
2003-06-11 18:04 ` Alexandre Oliva
2003-06-11 19:39 ` Maciej W. Rozycki
2003-06-11 20:39 ` Alexandre Oliva
2003-06-12 11:21 ` Maciej W. Rozycki
2003-06-12 12:10 ` Bernd Jendrissek
2003-06-12 12:26 ` Maciej W. Rozycki
2003-06-12 21:42 ` Alexandre Oliva
2003-06-13 10:35 ` Maciej W. Rozycki
2003-06-13 14:02 ` Alexandre Oliva
2003-06-13 18:32 ` Maciej W. Rozycki
2003-06-13 19:25 ` Alexandre Oliva
2003-06-13 20:15 ` Maciej W. Rozycki
2003-06-13 20:54 ` Alexandre Oliva
2003-06-14 14:33 ` Maciej W. Rozycki
2003-06-14 15:43 ` Alexandre Oliva
2003-06-14 18:27 ` Maciej W. Rozycki
2003-06-26 7:24 ` Alexandre Oliva
2003-06-28 0:35 ` Maciej W. Rozycki
2003-06-09 22:02 Daniel Jacobowitz
2003-06-09 22:17 ` Andrew Cagney
2003-06-09 22:34 ` Alexandre Oliva
2003-06-09 23:14 ` Daniel Jacobowitz
2003-06-10 0:44 ` 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=20030610014019.GA14933@doctormoo \
--to=neroden@twcny.rr.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.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).