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
To:	Christopher Faylor <cgf AT redhat DOT com>
Cc:	autoconf AT gnu DOT org, cygwin AT cygwin DOT com
Subject:	Re: Detecting the need for -mwin32 in newer cygwin gcc's
References:	<20010307161214 DOT A20717 AT redhat DOT com>
From:	Alexandre Oliva <oliva AT lsd DOT ic DOT unicamp DOT br>
Date:	07 Mar 2001 23:49:07 -0300
In-Reply-To:	<20010307161214.A20717@redhat.com>
Message-ID:	<orn1axvuu4.fsf@guarana.lsd.ic.unicamp.br>
Lines:	18
User-Agent:	Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version:	1.0

On Mar  7, 2001, Christopher Faylor <cgf AT redhat DOT com> wrote:

> Basically, I think we need something like a AC_PROG_GCC_USES_MWIN32.

I have mixed feelings about having this macro in autoconf.  On one
hand, it would be kind of promoting the use of proprietary software.
On the other, I see it would be a convenience for projects that really
need it, even though it could probably live with CFLAGS='-mwin32 -g -O2'.

I suppose a new macro could be posted to the autoconf macro archive
first, and, if lots of people agree autoconf is the right place for
this macro, we can eventually swallow it.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

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

- Raw text -