On 29 October 2012 00:08, Jonathan Wakely wrote: > Yes, libdir/gcc/target/version/../../../../include/c++/version would > be more accurate, because libdir is not necessarily /usr > > I'll come up with something better ...
I've committed this to the trunk.
commit 258a736d80af598109faeeeee44e55b057711d24 Author: Jonathan Wakely <jwakely....@gmail.com> Date: Thu Oct 18 00:32:07 2012 +0100 * doc/cpp.texi (Search Path): Fix outdated C++ path. diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi index fa5989e..c463e7c 100644 --- a/gcc/doc/cpp.texi +++ b/gcc/doc/cpp.texi @@ -856,7 +856,8 @@ requested with @code{@w{#include <@var{file}>}} in: /usr/include @end smallexample -For C++ programs, it will also look in @file{/usr/include/g++-v3}, +For C++ programs, it will also look in +@file{@var{libdir}/../include/c++/@var{version}}, first. In the above, @var{target} is the canonical name of the system GCC was configured to compile code for; often but not always the same as the canonical name of the system it runs on. @var{version} is the