Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Date:	Thu, 15 Mar 2001 18:56:37 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: updated win32 macro
Message-ID:	<20010315185637.A7724@redhat.com>
Reply-To:	cygwin-apps AT cygwin DOT com
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
References:	<20010315174916 DOT D6629 AT redhat DOT com> <000201c0ada6$0134fc80$a300a8c0 AT nhv>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<000201c0ada6$0134fc80$a300a8c0@nhv>; from nhv@cape.com on Thu, Mar 15, 2001 at 06:16:44PM -0500

On Thu, Mar 15, 2001 at 06:16:44PM -0500, Norman Vine wrote:
>Christopher Faylor writes:
>>>
>>>I would really like to minimse the alterations needed outside of
>>>configure.in - can you think of any package in particular 
>>likely to have
>>>trouble with CC=gcc -mwin32 ? (So that we could test it)
>>
>>Yes.  If you configure this way in the tcl directory and then 
>>cd .., the
>>tcl directory won't build because CC is overridden by the 
>>toplevel make.
>>
>>If you use CC='gcc -mwin32' configure in the top-level, then we might
>>as well just get rid of -mwin32 completely.  This will cause every
>>single package to be built with -mwin32 whether it needs it or not.
>
>FWIW
>
>I just built tcl the other day
>
>./configure --includedir=/usr/include/w32api
>make
>
>just worked :-)

We're trying to avoid telling people to include an additional
option.  That just doesn't work.

cgf

- Raw text -