Re: compiling with g++ 3.3

2003-06-15 Thread Nathan Poznick
Thus spake Shawn Lamson: > It actually doesn't look like it does search the /usr/include/g++-3/ > directory. > > ignoring nonexistent directory "/usr/i386-linux/include" > #include "..." search starts here: > #include <...> search starts here: > /usr/include/c++/3.3 > /usr/include/c++/3.3/i386-l

Re: compiling with g++ 3.3

2003-06-15 Thread Shawn Lamson
On Sun, 15 Jun 2003 01:59:12 -0500 Nathan Poznick <[EMAIL PROTECTED]> wrote: > Thus spake Shawn Lamson: > > I refer to page: > > http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/headers_cc.txt > > which lists iostream as a standard library header. So why throw the > > message from "backward/backw

Re: compiling with g++ 3.3

2003-06-15 Thread Nathan Poznick
Thus spake Shawn Lamson: > I refer to page: > http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/headers_cc.txt > which lists iostream as a standard library header. So why throw the > message from "backward/backward_warning.h" at me? > In addition, if I alter the #include to be > #include > then I