X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Message-ID: <4DEA7C01.7060409@cwilson.fastmail.fm>
Date: Sat, 04 Jun 2011 14:40:01 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Updated: mingw-runtime-3.18-3
References: <201106020502 DOT p5252MaN022999 AT alum-mailsec-relay-3 DOT mit DOT edu>	<BANLkTimjYTTneKq9Fyd2sqnidVwgD_nioQ AT mail DOT gmail DOT com> <BANLkTimZSmQm-UtZHkzGK4=yezSOCdSBUQ AT mail DOT gmail DOT com> <isdt55$9gu$1 AT dough DOT gmane DOT org>
In-Reply-To: <isdt55$9gu$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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 6/4/2011 2:22 PM, René Berber wrote:
> On 6/4/2011 12:49 PM, Jim Reisert AD1C wrote:
>> René Berber suggested:
>>
>>> Use i686-pc-mingw32-gcc instead.
>>
>> That worked, thanks.  That's not 100% correct, though, the command is
>> (or seems to be):
>>
>>   i686-w64-mingw32-gcc

No, the mingw-gcc(-core) package provides i686-pc-mingw32-gcc.exe.  The
mingw64-i686-gcc(-core) package provides i686-w64-mingw32-gcc.exe.

The difference between the two is:
1) mingw-gcc (that is, i686-pc-mingw32-*) is based on the mingw.org
distribution. It uses the mingw-runtime (e.g. msvcrt implibs & headers)
and w32api headers developed by that project -- which happen to be the
same as the ones used by the cygwin project itself.

2) mingw64-i686-gcc (that is, i686-w64-mingw32-*) is based on the
mingw64.sf.net distribution.  It uses a different, and independently
developed, version of the msvcrt implibs, headers, and w32api headers.
It shares this distinction with the mingw64-x86_64-gcc (that is,
x86_64-w64-mingw32-*) compiler.  However, the i686-w64 version creates
32bit output -- ONLY.  the x86_64-w64 version creates 64bit output ONLY.

Furthermore, both the i686-w64 and x86_64-w64 versions use "sjlj"
exception handling, while the i686-pc version uses "dw2" exception handling.

> One is for 32-bit the other for 64-bit, but the 64-bit is supposed to be
> capable of producing both kind of binaries, I don't use it so I'm not
> sure if they reached that objective.

This is completely wrong.

--
Chuck


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