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/66932] Preprocessor includes wrong header file Date: Sun, 18 Jul 2021 23:03:51 +0000 [thread overview] Message-ID: <bug-66932-4-8oDyJNy6pa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66932-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66932 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The problem is you have -I. and C_INCLUDE_PATH including the cwd ".". from the documentation: https://gcc.gnu.org/onlinedocs/cpp/Invocation.html#Invocation: If a standard system include directory, or a directory specified with -isystem, is also specified with -I, the -I option is ignored. ---- CUT ----- C_INCLUDE_PATH is considered similar to -isystem but after processing the commandline options. So this is not a bug really except just a minor wording there might improve dealing with the envs.
prev parent reply other threads:[~2021-07-18 23:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-18 19:54 [Bug preprocessor/66932] New: " pilot.mm at gmail dot com 2015-07-19 2:49 ` [Bug preprocessor/66932] " pinskia at gcc dot gnu.org 2015-07-19 13:42 ` redi at gcc dot gnu.org 2015-07-19 17:51 ` pilot.mm at gmail dot com 2015-07-20 9:27 ` pinskia at gcc dot gnu.org 2021-07-18 23:03 ` pinskia at gcc dot gnu.org [this message]
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-66932-4-8oDyJNy6pa@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).