public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: mingw.org cross compiler [Was: problem with cvs binary?]
Date: Tue, 16 Jul 2013 15:52:00 -0000	[thread overview]
Message-ID: <51E5693E.9090207@cwilson.fastmail.fm> (raw)
In-Reply-To: <20130716131044.GJ2712@calimero.vinschen.de>

On 7/16/2013 9:10 AM, Corinna Vinschen wrote:
> Are the mingw cross compilers still necessary, now that we have
> modern mingw-w64 toolchains?  On Fedora they aren't shipped since
> F17, which already came with mingw-w64 toolchains either.

No, in the sense that you could use the mingw-w64 i686 toolchain to 
generate 32bit "native" windows apps instead.

Yes, because the two toolchains are not mutually compatible (different 
ABI, different exception model, different threading library, different 
w32api/runtime library). If you are using a cygwin $host to develop, 
specifically, mingw.org-distribution compatible apps/libs...then you 
need the mingw.org cross compiler.

I don't know how many people that represents -- it might just be me and 
Earnie -- but I'm not ready to declare mingw(.org)-gcc dead just yet.  I 
at least want to update our current offering to something more current 
than 4.5.x, AND it's necessary on i686 because recent gmp/mpfr/mpc 
library updates have broken mingw-gcc.  If, after this update, we want 
to declare EOL on mingw(.org)-gcc, we could discuss that on cygwin-apps.

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

  reply	other threads:[~2013-07-16 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  6:03 problem with cvs binary? Mark Levedahl
2013-07-16 13:30 ` Charles Wilson
2013-07-16 15:01   ` Corinna Vinschen
2013-07-16 15:52     ` Charles Wilson [this message]
2013-07-16 17:05       ` mingw.org cross compiler [Was: problem with cvs binary?] Earnie Boyd
2013-07-17  1:39         ` Charles Wilson

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=51E5693E.9090207@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).