This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Updating top-level autoconf to 2.59

From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: gcc-patches at gcc dot gnu dot org, binutils at sourceware dot org, newlib at sourceware dot org
Date: Thu, 08 Feb 2007 13:48:22 +0100
Subject: Re: Updating top-level autoconf to 2.59
References: <20061214194654.GA6243@nevyn.them.org> <200701112249.OAA12557@hpsje.cup.hp.com> <20070111225346.GA1335@nevyn.them.org> <20070207193352.GA13757@nevyn.them.org> <Pine.LNX.4.64.0702072344050.7123@digraph.polyomino.org.uk> <20070208032909.GA8419@nevyn.them.org> <45CADD5E.404@lu.unisi.ch> <Pine.LNX.4.64.0702081239290.12368@digraph.polyomino.org.uk>

Likewise - if building compilers for the same target and multiple hosts it seems at least nonintuitive that --target must be specified for most hosts but must not be specified for the one host that's the same as the target. And will target default to host in that case (if you specify host but not target) for 2.13?

IIRC, the problem is actually specifying --host, not --target. If you configure with just --build --target, it should work right. Still, I'd prefer to not change the semantics of this.

Paolo

Follow-Ups:
- Re: Updating top-level autoconf to 2.59
  - From: Joseph S. Myers

References:
- Re: Updating top-level autoconf to 2.59
  - From: Daniel Jacobowitz
- Re: Updating top-level autoconf to 2.59
  - From: Joseph S. Myers
- Re: Updating top-level autoconf to 2.59
  - From: Daniel Jacobowitz
- Re: Updating top-level autoconf to 2.59
  - From: Paolo Bonzini
- Re: Updating top-level autoconf to 2.59
  - From: Joseph S. Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]