Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199907012200.RAA24630@mercury.xraylith.wisc.edu>
To: Ian T Zimmerman <itz AT lbin DOT com>
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: include and library paths 
In-Reply-To: Your message of "01 Jul 1999 21:34:56 -0000."
             <873owfygmf DOT fsf AT amazon DOT lbin DOT com> 
Date: Thu, 01 Jul 1999 17:00:05 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Ian T Zimmerman <itz AT lbin DOT com> writes:
> >>>>> "Mumit" == Mumit Khan <khan AT xraylith DOT wisc DOT EDU> writes:
> 
>     Mumit> How about trying the "GCC" way -- use
>     Mumit> -I/usr/X11R6.4/include -I...?
> 
>     Mumit> My personal opinion -- C_INCLUDE_PATH etc should never be
>     Mumit> used. You should see the number of bug reports from people
>     Mumit> who "forget" that they have these variables set in the
>     Mumit> environment and of course gets the wrong include file and
>     Mumit> all hell breaks loose. I like -I, -L, etc options that are
>     Mumit> visible when compiling/linking a file.
> 
> Except that my original situation involved a configure failure.  I
> know that I can pass extra options like this
> 
> CPPFLAGS=-I/foo/bar configure
> 
> but that only works for GNU autoconf style scripts, and only the clean 
> ones among these.  (Ie. the ones that use CPPFLAGS and not some other
> home cooked name, and that initialize it from the environment.)
> 

Try ``CC="gcc -I/foo:/bar" configure'' instead of using CPPFLAGS. It's
usually a better bet when using not-so-well-behaved configure-style
script.

The bug has been fixed long since, so all you need to do is upgrade.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com