public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris dot litchfield at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/19541] need another option to support what -I- did just besides -iquote Date: Tue, 18 May 2010 19:49:00 -0000 [thread overview] Message-ID: <20100518194851.19204.qmail@sourceware.org> (raw) In-Reply-To: <bug-19541-8743@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from chris dot litchfield at gmail dot com 2010-05-18 19:48 ------- This is still a huge issue. We would wish to inhibit use of the CURRENT Working directory to find include files. Basically FORCE every time a new include file is found with #include to start AGAIN from the begining of the Include Path system. using -iquote will simply cause the same problem where an include file that includes another include file will include that sub-include file even if you can pulled it away in a previous include path. Make files with VPATH or put Development paths first in lists are totally hosed by removing the -I- functionality. This is NOT an enhancement but a Priority 2 bug which there is NO WORKAROUND provided by removing a feature. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19541
next prev parent reply other threads:[~2010-05-18 19:49 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19541-8743@http.gcc.gnu.org/bugzilla/> 2005-10-06 20:41 ` [Bug pch/19541] deprecation of -I- makes precompiled headers less usable rodolfo at rodsoft dot org 2006-04-12 20:19 ` [Bug preprocessor/19541] " pinskia at gcc dot gnu dot org 2006-04-13 16:45 ` [Bug preprocessor/19541] need another option to support what -I- did just besides -iquote pinskia at gcc dot gnu dot org 2007-03-02 21:58 ` levengcc at pleetveern dot com 2008-01-18 20:12 ` pinskia at gcc dot gnu dot org 2008-01-18 22:23 ` [Bug c/19541] " tromey at gcc dot gnu dot org 2008-01-19 1:06 ` ISPARRY at BROCADE dot COM 2008-07-30 15:41 ` dvilleneuve at kronos dot com 2008-07-30 17:45 ` tromey at gcc dot gnu dot org 2008-08-30 23:32 ` pinskia at gcc dot gnu dot org 2008-08-30 23:39 ` pinskia at gcc dot gnu dot org 2009-01-14 12:19 ` Johannes dot Schwenke at gmx dot de 2010-05-18 19:49 ` chris dot litchfield at gmail dot com [this message] [not found] <bug-19541-4@http.gcc.gnu.org/bugzilla/> 2010-12-06 20:07 ` fergusoc at us dot ibm.com 2010-12-06 20:13 ` chris.litchfield at gmail dot com 2010-12-08 15:59 ` fergusoc at us dot ibm.com 2010-12-08 16:11 ` chris.litchfield at gmail dot com 2011-02-14 22:54 ` pinskia at gcc dot gnu.org 2011-06-28 14:15 ` jdrosa at yahoo dot com 2012-02-02 13:40 ` achurch+gcc at achurch dot org 2013-06-16 14:52 ` rodolfo at rodsoft 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=20100518194851.19204.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).