This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
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
- To: nobody at gcc dot gnu dot 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
- From: "Zack Weinberg" <zackw at stanford dot edu>
- Date: 20 Jun 2001 01:16:02 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: "Zack Weinberg" <zackw at stanford dot edu>
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_