This is the mail archive of the
mailing list for the Cygwin project.
Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
- To: Cygwin Apps <cygwin-apps at cygwin dot com>
- Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Fri, 20 Apr 2001 14:50:20 -0400
- References: <3AE07A27.3AAC7BE5@yahoo.com>
- Reply-To: cygwin-apps at cygwin dot com
On Fri, Apr 20, 2001 at 02:04:23PM -0400, Earnie Boyd wrote:
>I've just successfully completed building a Cygwin native cross build
>environment for --target=mingw32. While I'm cleaning up the code
>modifications I would like to ask if we should consider deprecating the
>-mno-cygwin switch in favor of the cross environment?
>I would rather see the cross build environment become standard because
>it is a natural for autoconfiguration. You just add --host=mingw32 to
>the configuration scripts instead of needing to do CC='gcc -mno-cygwin'
>configure ... .
Without gettin too much into the semantics of the word "deprecate", I
think it makes sense to strongly discourage use of -mno-cygwin if there
is a true cross-compiler available.
So, are you proposing that you will maintain a i686-pc-mingw32-gcc port,
Earnie? One problem is that this will mean keeping at least a separate
version of binutils/ld, too, since ld has some builtin defaults that
may not be appropriate for mingw.