From: Alexandre Oliva <aoliva@redhat.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: Partial autoconf transition thoughts
Date: Tue, 10 Jun 2003 22:06:00 -0000 [thread overview]
Message-ID: <orr861k2om.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <Pine.GSO.3.96.1030610124705.19547C-100000@delta.ds2.pg.gda.pl>
On Jun 10, 2003, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:
> Well, if I specify --host, I mean I want to use a different alias than
> the one that is expanded by config.sub.
--host has absolutely nothing to do with config.sub. --host defaults
to --build, that defaults to the output of config.guess. If you want
to override --build, just do it, and it will be propagated to host as
well. If you mean to specify different --build and --hosts, that's a
cross. If you specify --build and --host and they're identical,
that's a native for now, but it'll eventually be a cross because
there's no point in specifying --host if you don't want a cross.
> The change is not purely internal
> to the compilation process -- there are examples, binutils and gcc
> inclusive, where this alias gets propagated to file names, e.g. as a
> prefix to executables or as a name of the tooldir.
That's --target, something entirely different.
> I'd like to see this capability preserved, not necessarily exactly the
> way it's being done now. One possibility for host_alias and also
> target_alias is to default to build_alias and host_alias instead of host
> and target, respectively, as it happens now.
Huh? Where is it that host_alias defaults to build or build_alias?
In autoconf, it defaults to neither. If --host is not specified,
host_alias remains blank, not the same as build_alias, not the same as
nonopt, not the same as the output of config.guess. Nathan was kind
enough to write macros that do exactly what you want, AFAICT, setting
{build,host,target}_noncanonical, which is what we'd now use for what
we used to use {build,host,target}_alias, whose meaning is slightly
different in autoconf 2.5x. I.e., it does what you already.
--
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:[~2003-06-10 22:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 1:40 Nathanael Nerode
2003-06-10 1:46 ` DJ Delorie
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=orr861k2om.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=macro@ds2.pg.gda.pl \
--cc=neroden@twcny.rr.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).