This is the mail archive of the
mailing list for the Cygwin project.
Re: mingw.org cross compiler [Was: problem with cvs binary?]
- From: Earnie Boyd <earnie at users dot sourceforge dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 16 Jul 2013 12:25:09 -0400
- Subject: Re: mingw.org cross compiler [Was: problem with cvs binary?]
- References: <ks2e8i$idp$1 at ger dot gmane dot org> <51E54596 dot 5040400 at cwilson dot fastmail dot fm> <20130716131044 dot GJ2712 at calimero dot vinschen dot de> <51E5693E dot 9090207 at cwilson dot fastmail dot fm>
On Tue, Jul 16, 2013 at 11:39 AM, Charles Wilson wrote:
> 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
I'm not actually using mingw-gcc on Cygwin and have no opinion for the offering.
> 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.
Can you specify what the issues are for gmp/mpfr/mpc? I ask because
I'm attempting to build 2.8.1.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple