public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/31186] -I/usr/include not taken into account Date: Sat, 28 Aug 2021 03:45:04 +0000 [thread overview] Message-ID: <bug-31186-4-YofpvnbMBG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-31186-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31186 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The remaining environment variables apply only when preprocessing the particular language indicated. Each specifies a list of directories to be searched as if specified with -isystem, but after any paths given with -isystem options on the command line. If a standard system include directory, or a directory specified with -isystem, is also specified with -I, the -I option is ignored. The directory is still searched but as a system directory at its normal position in the system include chain. This is to ensure that GCC’s procedure to fix buggy system headers and the ordering for the #include_next directive are not inadvertently changed. If you really need to change the search order for system directories, use the -nostdinc and/or -isystem options. See System Headers. This part specifically: If you really need to change the search order for system directories, use the -nostdinc and/or -isystem options.
next parent reply other threads:[~2021-08-28 3:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-31186-4@http.gcc.gnu.org/bugzilla/> 2021-08-28 3:45 ` pinskia at gcc dot gnu.org [this message] 2021-08-28 10:37 ` vincent-gcc at vinc17 dot net 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
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=bug-31186-4-YofpvnbMBG@http.gcc.gnu.org/bugzilla/ \ --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).