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 09:07:10 -0500
Message-ID: <20010301140710.28473.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin AT cygwin DOT com
CC: cygwin AT cygwin DOT com
In-reply-to: <3A9E54BA.29FF0918@yahoo.com> (message from Earnie Boyd on Thu,
	01 Mar 2001 08:55:06 -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> <20010301131515 DOT 28102 DOT qmail AT lizard DOT curl DOT com> <3A9E54BA DOT 29FF0918 AT yahoo DOT com>

>  Date: Thu, 01 Mar 2001 08:55:06 -0500
>  From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
>  
>  Did you even stop to think that I might know exactly what I'm
>  saying and try it?!?!?!?!?!?!?!?

I know you know exactly what you are saying.  I know it makes Make
compile successfully.  But again, this was not my point.  As I said in
my initial message, I already knew how to work around the problem.

>  You obviously don't understand configure or autoconf.

I have been using configure and autoconf since they were first
released.  I have submitted patches to configure scripts in various
free-software packages, and to autoconf itself, on numerous occasions.
I have been using and submitting bug reports and fixes for GNU
software for over thirteen years.  I understand both configure and
autoconf quite well, thank you.

I did not insult you; why are you insulting me?

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

Well, yes, that was exactly my point, so why are you flaming me
obnoxiously?

Configure is supposed to figure out how to invoke the compiler
correctly so that the developer doesn't have to.  Configure is
supposed to know, "On this platform, you need to call gcc with these
flags to get it to work properly."

In other words, somebody who understands how "gcc -mwin32", etc. work
on Cygwin needs to modify autoconf's macros so that they include a
check which says, "If we're on Cygwin and compiling with gcc, add
-mwin32 to its flags," and then the maintainers of the various
packages that compile under Cygwin, either the generic package (if it
compiles out of the box) or the Cygwin-specific version of it, need to
add code to their configure.in scripts to call that check.

>  What "Cygwin package" are you referring to?

Well, for one, the one I already mentioned, Make.

My point is very simple.  The main point of configure is that
"configure; make" should work without the person running it needing to
do any additional configuration.  If the person running it needs to do
additional configuration, then the configure script needs to be
updated somehow.  That's all there is to it.  All I'm asking is, is
the fact that "-mwin32" is now required and wasn't before going to be
reflected in autoconf and in the configure scripts used to compile the
various packages that compile under Cygwin?

  jik

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