public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/31186] -I/usr/include not taken into account
Date: Tue, 22 May 2007 18:11:00 -0000 [thread overview]
Message-ID: <20070522181130.25904.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31186-6373@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from tromey at gcc dot gnu dot org 2007-05-22 19:11 -------
My recollection is that the special -I behavior is there because
the system headers have special non-warning properties.
This situation doesn't apply to -L.
> 2. Software is often compiled with configure, make, make install. How can one
> force the compiler to look in /usr/include & /usr/lib first (i.e. override the
> user's environment)?
Generally speaking this is not a good idea. Usually people *want* their
environment to influence configure, and usually if configure overrides this
it means difficult to fix problems on weirder systems.
I am leaving this open considering that there is still a documentation bug
to be fixed here.
--
tromey at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-05-22 19:11:27
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31186
next prev parent reply other threads:[~2007-05-22 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 14:22 [Bug preprocessor/31186] New: " vincent at vinc17 dot org
2007-03-15 15:48 ` [Bug preprocessor/31186] " pinskia at gcc dot gnu dot org
2007-03-15 16:51 ` vincent at vinc17 dot org
2007-05-22 18:11 ` tromey at gcc dot gnu dot org [this message]
2007-05-22 21:51 ` vincent at vinc17 dot org
[not found] <bug-31186-4@http.gcc.gnu.org/bugzilla/>
2021-08-28 3:45 ` pinskia at gcc dot gnu.org
2021-08-28 10:37 ` vincent-gcc at vinc17 dot net
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=20070522181130.25904.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).