This is the mail archive of the cygwin 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: Eliminating -mno-cygwin from gcc?

Hash: SHA1

According to Christopher Faylor on 1/31/2007 6:13 AM:
> How about if we eliminate -mno-cygwin from future releases and either
> provide our own mingw cross-tools or wrap the offerings from
> This would mean that instead of saying 'gcc -mno-cygwin', you'd say:
> 'i686-mingw-gcc' which would, I know, make a few computers spontaneously
> self-destruct however, I really don't think that the -mno-cygwin belongs
> in gcc.  No other port of gcc has anything like this.

Fine by me, especially since when TRYING to cross compile, autoconf issues
a nasty warning:

$ ../configure --host=i686-pc-mingw32 --build=i686-pc-cygwin \
  CC='gcc -mno-cygwin' host_alias=i686-pc-mingw32
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-mingw32-strip... no
checking for strip... strip
configure: WARNING: In the future, Autoconf will not detect cross-tools
whose name does not start with the host triplet.  If you think this
configuration is useful to you, please write to
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-mingw32

I would much rather call the cross-compiler i686-mingw-gcc than the
current name of 'gcc -mno-cygwin'.

- --
Don't work too hard, make some time for fun as well!

Eric Blake   
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -


Unsubscribe info:
Problem reports:

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