Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 18 Oct 2000 10:51:41 -0400
Message-Id: <200010181451.KAA12316@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: fjh AT cs DOT mu DOT oz DOT au
CC: earnie_boyd AT yahoo DOT com, cygwin AT sources DOT redhat DOT com
In-reply-to: <20001019014420.A18851@hg.cs.mu.oz.au> (message from Fergus
	Henderson on Thu, 19 Oct 2000 01:44:20 +1100)
Subject: Re: Does Cygwin's `-mno-cygwin' need Mingw?
References: <20001016174011 DOT 23903 DOT qmail AT web111 DOT yahoomail DOT com> <20001019014420 DOT A18851 AT hg DOT cs DOT mu DOT oz DOT au>


> 	- Is there much difference between the two?

There should be no difference between the resulting executables,
provided someone merges the two runtimes again.

The big difference is that "cygwin" is a collection of GNU programs
that use the cygwin runtime, while "mingw" is a collection of GNU
programs that use the MS runtime.

> 	- Is there an official name for the `-mno-cygwin' option of Cygwin?
> 	  "The -mno-cygwin switch of the Cygwin product" is a bit wordy.
> 	  (Perhaps it should be called "Clayton's Cygwin" ;-)

There is never a short name for a cross compiler

> 	- Cygwin and "Cygwin -mno-cygwin" are sufficiently different that
> 	  I think it would make sense for them to have different autoconf
> 	  canonical system names -- after all, Mingw has a different name,
> 	  and "Cygwin -mno-cygwin" is closer to Mingw than to Cygwin.
> 	  Currently autoconf seems to configure as "i*86-pc-cygwin",
> 	  even if you invoke configure as "CC='gcc -mno-cygwin' ./configure".
> 	  Should it configure report the host system type as "i*86-pc-mingw"
> 	  in that situation?  Or should we invent a new name for that?

Cygwin will always identify itself as a cygwin runtime.  If you build
under mingw, then it should have a "uname" that identifies itself as
mingw.  If you want to build with -mno-cygwin, you basically are
building a cross compiler, and need to follow the cross compiler
instructions (which are more involved than "-mno-cygwin" would have
you believe).

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com