This is the mail archive of the
mailing list for the Cygwin project.
Re: include and library paths
- To: firstname.lastname@example.org
- Subject: Re: include and library paths
- From: Mumit Khan <email@example.com.EDU>
- Date: Thu, 01 Jul 1999 16:15:23 -0500
- cc: Ian T Zimmerman <firstname.lastname@example.org>
Chris Faylor <email@example.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
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.
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.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org