X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <AANLkTi=AZoHDHVbbyiSe99WnKUDOmdwYnVvLTfwV5e7W@mail.gmail.com>
References: <30467239 DOT post AT talk DOT nabble DOT com>	<AANLkTikCqUhVfD71CGGn6WsTASAgYVmjX2SBLoy+XgWb AT mail DOT gmail DOT com>	<AANLkTinCuy-W_qdv5oR8GY664qCfPPeJ7M6jR3oSDSSK AT mail DOT gmail DOT com>	<AANLkTi=oe9uXBpKQE1iyz2PB90F0ymVBB8vbrhKftYRm AT mail DOT gmail DOT com>	<AANLkTi=WVja3R5SN025yOModPBu_LttOqNQdyZSQ2PE7 AT mail DOT gmail DOT com>	<AANLkTi=AZoHDHVbbyiSe99WnKUDOmdwYnVvLTfwV5e7W AT mail DOT gmail DOT com>
Date: Wed, 22 Dec 2010 10:53:36 -0500
Message-ID: <AANLkTikALVRkzvOdO+VNLKNBsfC2fd4V3nyQu-gzoqdN@mail.gmail.com>
Subject: Re: mingw-targeted cross-compiler question
From: NightStrike <nightstrike AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Wed, Dec 22, 2010 at 10:35 AM, Andy Koppe <andy DOT koppe AT gmail DOT com> wrote:
> On 22 December 2010 15:12, NightStrike wrote:
>> 2010/12/22 Fr=E9d=E9ric Bron:
>>>>>> I checked the Make file, it used this flag:
>>>>>> gcc -mno-cygwin -g -Wl,--add-stdcall-alias -Wl,--export-all-symbols =
...
>>>>>
>>>>> replace gcc by gcc-3
>>>>> gcc 4 is now the default on cygwin but the cross compiler is not
>>>>> supported for that version.
>>>>> Fr=E9d=E9ric
>>>>
>>>> What do you mean by not supported? =A0JonY maintains the cross compile=
rs....
>>>
>>> I meant that i686-w64-mingw32-gcc exists but not i686-w32-mingw32-gcc.
>>> I thought that w64 meant "built on win64" and mingw32 "run binary on wi=
n32".
>>> So it seems to me that with cygwin running on a 32 bit windows, it is
>>> not possible to cross compile to win32. However with a 64 bit windows
>>> you can produce win32 applications.
>>> However, I just tried to use i686-w64-mingw32-g++ on my win32 machine
>>> with a hello world program and it produces an binary that can be used
>>> from windows on that win32 machine.
>>> So my question to the list: what is the meaning of w64 in the name?
>>
>> Basically, "stuff from mingw-w64.sf.net"
>>
>> The middle piece of the triplet is the vendor tag. =A0We at mingw-w64
>> are the vendors. =A0We support win32 and win64, for both host and
>> target. =A0I admit it's confusing, but we didn't come up with a better
>> name fast enough.
>
> Also, the 'mingw32' in the OS part of the triplet is hystorical
> ballast. The '32' in there doesn't mean anything (anymore), and a
> better name would have been plain 'mingw' or even just 'windows'.
> Alas, compatibility concerns have stopped any change.

You should be able to safely drop the 32 at the very least with recent
versions of config.*

I thought we changed most things to check for mingw* instead of mingw32.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple