On Sun, 21 Oct 2012, Jonathan Wakely wrote: >> I was going to say "Ack", since it's a doc patch, but somehow my >> own tests on various platforms (FreeBSD, GNU/Linux,...) did not >> confirm /usr/include/c++ in the search path. >> >> Or do you mean that it's at the root of some search paths, that >> is /usr/include/c++/... instead of /usr/include/g++-v3 ? (I >> definitely have not seen the latter anywhere, so if it's this, >> then it looks okay.) > I get: > > echo | g++ -v -E -x c++ - 2>&1 | sed -n '/#include <...> search > starts/,/End of search list/p' > #include <...> search starts here: > /usr/lib/gcc/x86_64-redhat-linux/4.6.3/../../../../include/c++/4.6.3 > > /usr/lib/gcc/x86_64-redhat-linux/4.6.3/../../../../include/c++/4.6.3/x86_64-redhat-linux > /usr/lib/gcc/x86_64-redhat-linux/4.6.3/../../../../include/c++/4.6.3/backward > /usr/lib/gcc/x86_64-redhat-linux/4.6.3/include > /usr/local/include > /usr/include > End of search list. > > And: > > readlink -f > /usr/lib/gcc/x86_64-redhat-linux/4.6.3/../../../../include/c++/4.6.3 > /usr/include/c++/4.6.3
Yep, just I first read the text as /usr/include/c++ itself being in the include path (which it is not). Of course, g++-v3 is even more incorrecot :-), so the patch is fine. Perhaps you can rephrase it a bit to help clarify that? (But that is optional; in any case, your patch improves what is currently there.) Gerald
