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
X-Apparently-From:	<earnie?boyd AT yahoo DOT com>
Message-ID:	<3A9E54BA.29FF0918@yahoo.com>
Date:	Thu, 01 Mar 2001 08:55:06 -0500
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	Earnie Boyd <cygwin AT cygwin DOT com>
X-Mailer:	Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	Jonathan Kamens <jik AT curl DOT com>
CC:	cygwin AT cygwin DOT com
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> <20010301131515 DOT 28102 DOT qmail AT lizard DOT curl DOT com>

Jonathan Kamens wrote:
> 
> >  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.
> 

Did you even stop to think that I might know exactly what I'm saying and
try it?!?!?!?!?!?!?!?

> Shouldn't "configure" for a Cygwin source package just Do The Right
> Thing?  

Configure doesn't know that you want to use /usr/include/w32api.  Adding
CC='gcc -mwin32' will cause the appropriate macros and switches to be
applied to the compiler.  You state in before configure so that
configure can build your Makefile with the CC variable set correctly.

> That's the whole point of "configure", isn't it?  

Configure has to make assumptions, sometimes those assumptions don't fit
so you have to control 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?
> 

You obviously don't understand configure or autoconf.  Also, this is a
recent change and some package configurations will have to go through a
few changes if the w32api headers are to be used.  What "Cygwin package"
are you referring to?  Cygwin is trying it's best to emulate UNIX/POSIX
and should by default not know about Win32 functions so this should be
an uncommon issue.  However Cygwin has been around long enough for
coding such as
  #if defined(_WIN32) || defined(__CYGWIN__)
  #include <windows.h>
  #endif
to exist.  If you wish to use the w32api with GCC-2.95.2-7 then you must
  CC='gcc -mwin32' ../configure
without exception.

Earnie.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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

- Raw text -