X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<op.vn4byplj5o90vo@orion>
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> <op DOT vn4byplj5o90vo AT orion>
Date:	Wed, 22 Dec 2010 15:11:18 +0100
Message-ID:	<AANLkTi=7ttVmyTupCkao16dPapL9Q0vPwe3c87Q-Xkd2@mail.gmail.com>
Subject:	Re: mingw-targeted cross-compiler question
From:	Kai Tietz <ktietz70 AT googlemail 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

2010/12/22  <lemkemch AT t-online DOT de>:
> On Wed, 22 Dec 2010 14:13:15 +0100, Fr=E9d=E9ric Bron <frederic DOT bron AT m4x.=
org>
> wrote:
>
>>>>> 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
>>> compilers....
>>
>> 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
>> win32".
>> 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?
>
> Well, I don't know but I'd really like to know what is the replacement
> these days for
>
> gcc -mno-cygwin -mwindows x.c
>
> I tried
>
> i686-w64-mingw32-gcc -mwindows =A0-m32 x.c
>
> but get
>
> x.c:35:13: error: expected '=3D', ',', ';', 'asm' or '__attribute__' befo=
re
> 'WinMain'
>
> and that also for all other option combinations that made sense to me.
>
> Thanks,
> Michael

Hi,

the -w64- within cross-compiler's triplet means that this compiler
uses mingw-w64 runtime headers and libraries. The architecture part of
triplet (i686|x86_64) makes the difference, if a cross-compiler
produces binaries for i686 (means 32-bit), or for x86_64  (means
64-bit) windows native.
Btw the -m32 is superflous for the i686-w64-mingw32 cross-compiler, as
it just produces 32-bit and has no 64-bit capabilities builtin.
Could you show please your x.c file, as the message you get is a
compiler error already. I would assume that you missed to include some
header, or you were defining something which cause here the harm.

Regards,
Kai


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

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