This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Updating top-level autoconf to 2.59
- From: Mike Stump <mrs at apple dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Daniel Jacobowitz <drow at false dot org>, gcc-patches at gcc dot gnu dot org, binutils at sourceware dot org, newlib at sourceware dot org
- Date: Wed, 7 Feb 2007 18:30:24 -0800
- 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>
On Feb 7, 2007, at 3:51 PM, Joseph S. Myers wrote:
With this patch, configuring with --build=i686-pc-linux-gnu --
host=i686-pc-linux-gnu --target=i686-pc-linux-gnu all specified
explicitly results in i686-pc-linux-gnu-gcc and i686-pc-linux-gnu-
i686-pc-linux-gnu-gcc being installed but no plain "gcc".
Installing i686-pc-linux-gnu-i686-pc-linux-gnu-gcc is clearly wrong
and existing practice is that "gcc" is installed whenever the host
and target are the same, regardless of the build system and
regardless of what was or was not specified explicitly.
As I recall, this was previously discussed and an intentional change
in behavior in autoconf. The solution is to build with just --
host=i686-pc-linux-gnu.