This is the mail archive of the
mailing list for the Cygwin project.
Re: include and library paths
- To: Ian T Zimmerman <email@example.com>
- Subject: Re: include and library paths
- From: Mumit Khan <firstname.lastname@example.org.EDU>
- Date: Thu, 01 Jul 1999 17:00:05 -0500
- cc: email@example.com
Ian T Zimmerman <firstname.lastname@example.org> writes:
> >>>>> "Mumit" == Mumit Khan <email@example.com.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
The bug has been fixed long since, so all you need to do is upgrade.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org