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:	<199907012115.QAA21177@mercury.xraylith.wisc.edu>
To:	cygwin AT sourceware DOT cygnus DOT com
cc:	Ian T Zimmerman <itz AT lbin DOT com>
Subject:	Re: include and library paths
In-Reply-To:	Your message of "Thu, 01 Jul 1999 16:51:54 EDT."
	<19990701165154 DOT C1292 AT cygnus DOT com>
Date:	Thu, 01 Jul 1999 16:15:23 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris Faylor <cygwin AT sourceware DOT cygnus DOT com> writes:
> On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman wrote:
> >amazon:~$ gcc -v -E stupid_test.c
> >Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egc
> s-2.91.57\specs
   ^^^^^^^

In any new port, GCC moves much faster than compared to a stable port;
x86-win32 happens to be one where every release fixes tons of bugs,
and 2.91.57 (aka egcs-1.1) is considered ancient by now.

It's one of about 150 known bugs.
  
> Ok, next, how about a:
> 
> ls /usr/X116.4/LessTif/Motif2.0/include /usr/X11R6.4/include
> 
> ?
> 
> If those work then I'll leave this to Mumit to comment.
> 

Upgrade.

How about trying the "GCC" way -- use -I/usr/X11R6.4/include -I...?

My personal opinion -- C_INCLUDE_PATH etc should never be used. You should
see the number of bug reports from people who "forget" that they have these
variables set in the environment and of course gets the wrong include file
and all hell breaks loose. I like -I, -L, etc options that are visible when
compiling/linking a file.

Regards,
Mumit


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

- Raw text -