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: Thu, 8 Mar 2001 11:53:56 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
Cc: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>,
        Alexandre Oliva <oliva AT lsd DOT ic DOT unicamp DOT br>, autoconf AT gnu DOT org,
        cygwin AT cygwin DOT com
Subject: Re: Detecting the need for -mwin32 in newer cygwin gcc's
Message-ID: <20010308115356.A3813@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>,
	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>,
	Alexandre Oliva <oliva AT lsd DOT ic DOT unicamp DOT br>, autoconf AT gnu DOT org,
	cygwin AT cygwin DOT com
References: <20010307161214 DOT A20717 AT redhat DOT com><orn1axvuu4 DOT fsf AT guarana DOT lsd DOT ic DOT unicamp DOT br><3AA74730 DOT D4C575FC AT ece DOT gatech DOT edu> <ork860sfhi DOT fsf AT guarana DOT lsd DOT ic DOT unicamp DOT br> <006d01c0a7c5$dd3b97c0$0200a8c0 AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <006d01c0a7c5$dd3b97c0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Mar 08, 2001 at 10:49:33PM +1100

On Thu, Mar 08, 2001 at 10:49:33PM +1100, Robert Collins wrote:
>cygwin, win32
>cygwin, nowin32
>no cygwin (aka mingw32), win32
>no cygwin, nowin32

-mno-cygwin and -mnowin32 is not an allowed combination.

Please, let's not complicate this.  The only thing required is a check
for -mwin32.

I'm not sure what all of the fuss is about.  autoconf is a method for
determining system configurations and oddities.  If a package maintainer
wants to write a configure.in which automatically detects when it is
running on Windows, using a cygwin version of gcc to build things, I
don't see why he shouldn't have a macro to accomodate the oddities of
cygwin gcc.

If this kind of macro isn't available in some fashion, then we leave
every package maintainer to reimplement the check in their own fashion.
To me, that is counter to what autoconf is all about.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple