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
To: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: include and library paths
References: <199907012115 DOT QAA21177 AT mercury DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Ian T Zimmerman <itz AT lbin DOT com>
Date: 01 Jul 1999 21:34:56 +0000
In-Reply-To: Mumit Khan's message of "Thu, 01 Jul 1999 16:15:23 -0500"
Message-ID: <873owfygmf.fsf@amazon.lbin.com>
Lines: 25
X-Mailer: Gnus v5.6.45/XEmacs 21.0(beta67) - "20 minutes to Nikko"

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

-- 
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107


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