From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: Updated: mingw-runtime-3.18-3
Date: Sat, 04 Jun 2011 18:40:00 -0000 [thread overview]
Message-ID: <4DEA7C01.7060409@cwilson.fastmail.fm> (raw)
In-Reply-To: <isdt55$9gu$1@dough.gmane.org>
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
prev parent reply other threads:[~2011-06-04 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201106020502.p5252MaN022999@alum-mailsec-relay-3.mit.edu>
2011-06-03 21:38 ` Jim Reisert AD1C
2011-06-03 22:11 ` René Berber
2011-06-04 1:01 ` JonY
2011-06-04 17:50 ` Jim Reisert AD1C
2011-06-04 18:22 ` René Berber
2011-06-04 18:40 ` Charles Wilson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DEA7C01.7060409@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).