From: Mumit Khan <khan@xraylith.wisc.EDU>
To: cygwin@sourceware.cygnus.com
Cc: Ian T Zimmerman <itz@lbin.com>
Subject: Re: include and library paths
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <199907012115.QAA21177@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990731183400.gZ6GB8103yPEuSlwKXMH5Y3I38DL-j5PjUt2hYak8hE@z> (raw)
In-Reply-To: <19990701165154.C1292@cygnus.com>
Chris Faylor <cygwin@sourceware.cygnus.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@sourceware.cygnus.com
next prev parent reply other threads:[~1999-07-31 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 11:53 Ian T Zimmerman
1999-07-01 12:19 ` Chris Faylor
1999-07-01 13:21 ` Ian T Zimmerman
1999-07-01 13:50 ` Chris Faylor
1999-07-01 14:11 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-01 14:15 ` Mumit Khan [this message]
1999-07-01 14:36 ` Ian T Zimmerman
1999-07-01 15:00 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-01 12:11 Earnie Boyd
1999-07-31 18:34 ` Earnie Boyd
1999-07-22 2:33 Joseph M. Hinkle
1999-07-31 18:34 ` Joseph M. Hinkle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199907012115.QAA21177@mercury.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=itz@lbin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).