This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: i686-pc-mingw32 cross compiler


On 10/28/2010 4:32 PM, Yaakov (Cygwin/X) wrote:
> I think we agreed to proceed with transitioning from the old gcc-3
> -mno-cygwin compilers to a true i686-pc-mingw32 cross-compiler
> environment.  This entails adding mingw-binutils, mingw-gcc (which would
> replace gcc-mingw-3.x), and rebuilding mingw-* to use the sysroot
> (including a new sysrooted mingw-w32api, separate from w32api in /usr).
> 
> The question is now, who is going to do this?
> 
> * gcc-mingw belongs to Dave Korn as it was part of gcc3 itself, but that
> connection is not necessary with a separate cross-compiler.
> 
> * mingw-runtime and w32api belong to Chris Sutcliffe.
> 
> * All other mingw-* packages belong ot Charles Wilson.
> 
> Chuck, since you maintain most of the mingw-* packages and are involved
> with mingw.org, you're the most logical choice.  FYI, my prototypes are
> now in Ports git:
> 
> http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=crossdevel
> 
> Are you planning to proceed with this, and when?

I've been using one of my own for a couple of months now (probably very
similar to yours).  I also worked thru the issues related to the "new"
required locations of the "mingw-runtime/w32api for the mingw cross
compiler" vs the "mingw-runtime/w32api for cygwin's compiler".  (e.g. my
"gcc-3 -mno-cygwin" compiler can use the mingw-cross-compiler's
mingw-runtime and w32api packages, with a little help). I documented
this here:
http://cygwin.com/ml/cygwin-apps/2010-07/msg00179.html


I actually have mingw-* packages (zlib|bzip|etc) built using that
toolchain ready to go -- or to be quickly rebuilt using the "real"
official cygwin->mingw toolchain.


However, I wasn't planning on releasing the new cross toolchain myself,
since IIRC Dave had sorta taken ownership of it (he owns gcc-3, with its
--mno-cygwin mode, after all).  Plus, I'm sorta clueless when it comes
to the innards of modern gcc; the last time I really dug into the guts
of gcc and binutils was around 2000.

OTOH, I'm probably the best liaison between "us" and mingw.org (well, me
or Chris Sutcliffe) since I'm active "over there".

I guess it boils down to this: I'm willing to package it and work thru
the initial teething pains, but I don't think I'm really qualified to
"support" the mingw cross compiler...unless...

We *could* take the position that: "We just package mingw.org's compiler
built as a cygwin-hosted cross toolchain.  We'll fix obvious packaging
bugs, and ensure that setup.exe can be built (as a reasonable "smoke
test"), but if there are any OTHER problems with the toolchain...go talk
to mingw.org"

However...to really "get away with that" attitude, we have to use the
mingw.org 'cross-build-script', because they only support toolchains
built using it.
https://sourceforge.net/projects/mingw/files_beta/Cross-Hosted%20MinGW%20Build%20Tool/x86-mingw32-build-1.0.1-rc1/

'Course, we might be able to work with them, and get them to extend that
attitude to "or the cygwin packaged version". That'll require some
negotiations, and we'll have to be very careful to ensure that "our"
mingw-cross toolchain is built exactly as their cross-tool-script would.
(Which is odd, because THEIR cross-tool-script configures the toolchain
*differently* that THEIR native one is configured -- and I'm not talking
about the obvious --build/--host issues).

--
Chuck


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]