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: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>,
        "Christopher Faylor" <cgf AT redhat DOT com>, <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>
	<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>
From: Alexandre Oliva <oliva AT lsd DOT ic DOT unicamp DOT br>
Date: 08 Mar 2001 10:02:08 -0300
In-Reply-To: <006d01c0a7c5$dd3b97c0$0200a8c0@lifelesswks>
Message-ID: <orsnkoqur3.fsf@guarana.lsd.ic.unicamp.br>
Lines: 21
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Mar  8, 2001, "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> wrote:

> Having set the stage above, you can see that squid uses autoconf to
> detect what features are available, before trying to compile them in,
> and that it is very reasonable for the developers to add fine tuned
> support for various core parts of squid using the win32 API

Sure.  In this case, I suppose pulling a macro from the autoconf macro
archive to detect the need for -mwin32 and calling it in their
configure.in wouldn't be asking too much.  After all, in any case,
they'd have to be aware of the need for calling the macro.

The only issue is whether to provide that macro in GNU autoconf or let
it evolve separately in the macro archive.  I think the latter is a
better approach, at least for now.

-- 
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