This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++ headers and system headers
- To: dewar at gnat dot com
- Subject: Re: libstdc++ headers and system headers
- From: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Date: Mon, 19 Feb 2001 01:42:54 +1100
- Cc: aoliva at redhat dot com, jbuck at synopsys dot COM, bkoz at redhat dot com, gcc at gcc dot gnu dot org, jason at redhat dot com, libstdc++ at gcc dot gnu dot org, neil at daikokuya dot demon dot co dot uk
- References: <20010218143559.675C0F289B@nile.gnat.com>
On 18-Feb-2001, dewar@gnat.com <dewar@gnat.com> wrote:
> I still can't see anywhere in the documentation where you could learn
> that -I/usr/include would break GCC ...
Well, the "Interoperation" section has the following (or at least it
did last November):
| * Use of `-I/usr/include' may cause trouble.
|
| Many systems come with header files that won't work with GCC unless
| corrected by `fixincludes'. The corrected header files go in a new
| directory; GCC searches this directory before `/usr/include'. If
| you use `-I/usr/include', this tells GCC to search `/usr/include'
| earlier on, before the corrected headers. The result is that you
| get the uncorrected header files.
However, the suggested course of action still uses `-I':
| Instead, you should use these options (when compiling C programs):
|
| -I/usr/local/lib/gcc-lib/TARGET/VERSION/include -I/usr/include
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
| of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.