Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: DJ Delorie <dj@redhat.com>
Cc: drow@mvista.com, binutils@sources.redhat.com, gcc@gcc.gnu.org,
	gdb@sources.redhat.com
Subject: Re: [toplevel] Gas install name problem from autoconf 2.5x
Date: Wed, 03 Sep 2003 16:13:00 -0000	[thread overview]
Message-ID: <m37k4psvd2.fsf@gossamer.airs.com> (raw)
In-Reply-To: <200309031531.h83FV7w03522@greed.delorie.com>

DJ Delorie <dj@redhat.com> writes:

> > How do we feel about migrating towards the new autoconf definitions -
> > i.e. anything with --host is cross-compiled, anything with --target is
> > a cross-compiler.
> 
> That breaks cases where you use --host to override config.guess's idea
> of the system name, i.e. to provide a canonical triplet across a range
> of build hosts that are compatible yet guess to different triples.

The new scheme is to specify --build instead.  $host defaults to
$build.

> It also breaks automated builds which aren't smart enough to even
> consider the possibility that you won't provide all three.  Er, like
> one of mine, which is table driven.

Yes.

> We should be liberal in what we accept.  We once discussed
> auto-detecting which autoconf each subdirectory used, and filtering
> command lines accordingly.  I suspect this is still a good idea.
> Don't expect the user to be smart about this, they won't be.

I think that is what is required until everything is updated.

It still leaves the top level problem--the behaviour changes at the
top level, which means that users have to change.

Ian


  reply	other threads:[~2003-09-03 16:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  4:10 Daniel Jacobowitz
2003-09-03  4:41 ` Ian Lance Taylor
2003-09-03 14:49   ` Daniel Jacobowitz
2003-09-03 15:31     ` DJ Delorie
2003-09-03 16:13       ` Ian Lance Taylor [this message]
2003-09-03 16:56         ` Daniel Jacobowitz
2003-09-04  5:40           ` Alexandre Oliva
2003-09-07  3:59             ` Daniel Jacobowitz
2003-09-07  4:08               ` Ian Lance Taylor
2003-09-07 17:33                 ` Daniel Jacobowitz
2003-09-03 16:12     ` Ian Lance Taylor
2003-09-04  5:37 ` 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=m37k4psvd2.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=drow@mvista.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