This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [PATCH] config.guess: Properly detect the *mingw32 targets

From: Kai Tietz <ktietz70 at googlemail dot com>
To: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Charles Wilson <mingw at cwilson dot fastmail dot fm>, Rainer Emrich <rainer at emrich-ebersheim dot de>, gcc-patches at gcc dot gnu dot org
Date: Thu, 12 Nov 2009 21:23:21 +0100
Subject: Re: [PATCH] config.guess: Properly detect the *mingw32 targets
References: <4AFBF07E.8070609@emrich-ebersheim.de> <4AFC0596.6040007@cwilson.fastmail.fm> <20091112201100.GC25110@gmx.de>

2009/11/12 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>:
> Why, BTW, does x86_64-w64-mingw32 have "32" in the name?

This is reasoned by a lot of testcases and configure parts shared with
i686-pc-mingw32. Sadly is at many point the triplet *-*-mingw32 used
instead of just *-*-mingw*

This 32 at the end is bogus for 32-bit and 64-bit, as the architecture
part describe this already.

Cheers,
Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

References:
- Re: [PATCH] config.guess: Properly detect the *mingw32 targets
  - From: Rainer Emrich
- Re: [PATCH] config.guess: Properly detect the *mingw32 targets
  - From: Charles Wilson
- Re: [PATCH] config.guess: Properly detect the *mingw32 targets
  - From: Ralf Wildenhues

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