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=WVja3R5SN025yOModPBu_LttOqNQdyZSQ2PE7@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>
Date:	Wed, 22 Dec 2010 15:35:53 +0000
Message-ID:	<AANLkTi=AZoHDHVbbyiSe99WnKUDOmdwYnVvLTfwV5e7W@mail.gmail.com>
Subject:	Re: mingw-targeted cross-compiler question
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 22 December 2010 15:12, NightStrike wrote:
> 2010/12/22 Fr=C3=A9d=C3=A9ric 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=C3=A9d=C3=A9ric
>>>
>>> What do you mean by not supported? =C2=A0JonY maintains the cross compi=
lers....
>>
>> 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 win=
32".
>> 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. =C2=A0We at mingw-w64
> are the vendors. =C2=A0We support win32 and win64, for both host and
> target. =C2=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.

Andy

--
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

- Raw text -