public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent at vinc17 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 21:51:00 -0000 [thread overview] Message-ID: <20070522215044.18629.qmail@sourceware.org> (raw) In-Reply-To: <bug-31186-6373@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from vincent at vinc17 dot org 2007-05-22 22:50 ------- (In reply to comment #3) > 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. But this introduces an inconsistency, with the effect that the version of the header and the version of the library do not match. > 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. But configure does override the user's environment for non-system directories (and even system directories concerning -L). That's not logical. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31186
next prev parent reply other threads:[~2007-05-22 21:51 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 2007-05-22 21:51 ` vincent at vinc17 dot org [this message] [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=20070522215044.18629.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: linkBe 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).