public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@stanford.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: preprocessor/3243: /usr/local/gcc-3.0/include/g++-v3/i686-pc-linux-gnu/bits/gthr.h:98:26: gthr-default.h: No such file or directory Date: Tue, 19 Jun 2001 18:16:00 -0000 [thread overview] Message-ID: <20010620011602.3502.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR preprocessor/3243; it has been noted by GNATS. From: "Zack Weinberg" <zackw@stanford.edu> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, carlo@alinoe.com Cc: Subject: Re: preprocessor/3243: /usr/local/gcc-3.0/include/g++-v3/i686-pc-linux-gnu/bits/gthr.h:98:26: gthr-default.h: No such file or directory Date: Tue, 19 Jun 2001 18:13:47 -0700 To clarify what Neil said: -I- has had the documented effect of separating "" and <> search paths, *and* inhibiting the search of the 'directory of the current file', since at least 2.7.2. -I- can indeed break system headers that expect the 'directory of the current file' to be searched. That may not be a good enough reason to change a feature with that length of tenure. I am all for separating the two effects, if we can agree on the interface and the degree of backward compatibility. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3243&database=gcc -- zw Well, there's another triumph for clean hands, a pure heart, a good soul...and vastly superior technology. -- _Undocumented Features: Out in the Cold_
next reply other threads:[~2001-06-19 18:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-19 18:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-20 13:26 Alexandre Oliva 2001-06-20 8:26 Carlo Wood 2001-06-19 13:36 Neil Booth 2001-06-19 6:27 aoliva
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=20010620011602.3502.qmail@sourceware.cygnus.com \ --to=zackw@stanford.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).