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: 1 Mar 2001 08:15:15 -0500
Message-ID: <20010301131515.28102.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin AT cygwin DOT com
In-reply-to: <3A9D8A11.C8221A95@yahoo.com> (message from Earnie Boyd on Wed,
	28 Feb 2001 18:30:25 -0500)
Subject: Re: Can't build Make from source because Windows header filesmoved to 
 /usr/include/w32api?
References: <20010228201025 DOT 6691 DOT qmail AT lizard DOT curl DOT com> <3A9D8A11 DOT C8221A95 AT yahoo DOT com>

>  Date: Wed, 28 Feb 2001 18:30:25 -0500
>  From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
>  
>  > I know how to work around this, but my question is.... Is this a known
>  > problem, what's the correct way to fix it, and when will it be fixed
>  > in the precompiled stuff being distributed by RedHat?
>  > 
>  
>  CC='gcc -mwin32' ../configure

Thanks, but I don't think this really answers my question.

Shouldn't "configure" for a Cygwin source package just Do The Right
Thing?  That's the whole point of "configure", isn't it?  So if some
Cygwin source packages depend on win32 header files or whatever,
shouldn't the configure script included with those packages
automatically add "-mwin32" or "-I/usr/include/w32api" or whatever to
the compiler flags?

  jik

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