public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jdrosa at yahoo 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, 28 Jun 2011 14:15:00 -0000 [thread overview]
Message-ID: <bug-19541-4-KRiUgokvGo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-19541-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19541
David Rosa <jdrosa at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jdrosa at yahoo dot com
--- Comment #21 from David Rosa <jdrosa at yahoo dot com> 2011-06-28 14:14:37 UTC ---
I want to add my voice to others who have asked that the priority of this bug
be elevated to P2.
Eliminating the secondary function of -I- as quoted from the GNU preprocessor
documentation is unacceptable.
"Second, the directory containing the current file is not searched for
anything, unless it happens to be one of the directories named by an -I
switch."
Even if a different switch is used, like the -ignore-source-dir I've heard some
rumblings about, can this issue please be elevated in priority and addressed
soon?
For our code base, we utilize gcc along with commercial cross-compilers. All of
the cross-compilers we use support an option that implements the original -I-
behavior and in order to maintain our existing code base, we either -I- to no
longer be deprecated or replaced with a different option that implements the
same behavior.
next prev parent reply other threads:[~2011-06-28 14:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2012-02-02 13:40 ` achurch+gcc at achurch dot org
2013-06-16 14:52 ` rodolfo at rodsoft dot org
2015-07-16 9:25 ` [Bug driver/19541] " melebius at gmail dot com
[not found] <bug-19541-8743@http.gcc.gnu.org/bugzilla/>
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
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-19541-4-KRiUgokvGo@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: 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).