This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: ITA: gcc-mingw-* gcc-3 -mno-cygwin support packages; ITP: mingw-binutils/mingw-gcc-* cross compiler
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps <cygwin-apps at cygwin dot com>
- Date: Tue, 11 Jan 2011 16:46:01 -0600
- Subject: Re: ITA: gcc-mingw-* gcc-3 -mno-cygwin support packages; ITP: mingw-binutils/mingw-gcc-* cross compiler
- References: <4CEC401E.4060506@cwilson.fastmail.fm> <20101124004126.GA14101@ednor.casa.cgf.cx> <4CEC883A.7000904@cwilson.fastmail.fm> <20101124050652.GB10552@ednor.casa.cgf.cx> <4CECA56F.3@cwilson.fastmail.fm> <4D0A45D5.6060509@cwilson.fastmail.fm>
On Thu, 2010-12-16 at 12:01 -0500, Charles Wilson wrote:
> cgf, any progress on creating a wrapper for mingw-binutils? If it's
> turning out to be difficult, could we go ahead with a "real"
> cross-configured mingw-binutils, and then maybe later update it with one
> that installs simple wrapper .exe's that munge argv[] and exec the
> cygwin binaries?
cgf,
I ask you to remove your objection and allow Chuck to proceed with his
mingw-binutils package. I know these would seem to be "identical" to
the native binutils, but the mingw- version has the hardcoded sysroot
which is necessary for a proper mingw-gcc.
Attempting to use wrapper scripts on top of cygwin binutils would be,
just like gcc -mno-cygwin was, the sort of fragile setup that I thought
we were trying to move away from. Treating mingw-* as a cross-compiling
environment just like any other is the much more reliable choice, even
if a little duplication is required.
Yaakov