Here's what I get:
yapn:eng@yapn:~/proj/aoeu> g++ --debug --verbose aoeu.C -o aoeu
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.0.2/configure
--prefix=/home/yapn/.mrm-vista/common/org/fsf/gcc/4.0.2
--exec-prefix=/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2
Thread model: posix
gcc version 4.0.2
/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2/libexec/gcc/i686-pc-linux-gnu/4.0.2/cc1plus
-quiet -v -D_GNU_SOURCE aoeu.C -quiet -dumpbase aoeu.C
-mtune=pentiumpro -auxbase aoeu -g -version -o /tmp/ccheq7Dt.s
ignoring nonexistent directory
"/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2/lib/gcc/i686-pc-linux-gnu/4.0.2/../../../../../../../../../../../../include/c++/4.0.2"
ignoring nonexistent directory
"/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2/lib/gcc/i686-pc-linux-gnu/4.0.2/../../../../../../../../../../../../include/c++/4.0.2/i686-pc-linux-gnu"
ignoring nonexistent directory
"/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2/lib/gcc/i686-pc-linux-gnu/4.0.2/../../../../../../../../../../../../include/c++/4.0.2/backward"
ignoring nonexistent directory
"/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2/lib/gcc/i686-pc-linux-gnu/4.0.2/../../../../../../../../../../../i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/home/yapn/.mrm-vista/common/org/fsf/gcc/4.0.2/include
/home/yapn/.mrm-vista/kernel/org/fsf/gcc/4.0.2/lib/gcc/i686-pc-linux-gnu/4.0.2/include
/usr/include
End of search list.
GNU C++ version 4.0.2 (i686-pc-linux-gnu)
compiled by GNU C version 3.2.2 20030222 (Red Hat Linux 3.2.2-5).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
aoeu.C:1:20: error: iostream: No such file or directory
aoeu.C: In function 'int main(int, char**)':
aoeu.C:6: error: 'cout' is not a member of 'std'
aoeu.C:6: error: 'endl' is not a member of 'std'
On 10/28/05, Noel Yap <noel.yap@xxxxxxxxx> wrote:
> What do I need to do to build gcc 4.0, such that when using it, it
> knows where its own header files are. IOW, such that the compile
> implitly uses -I path/to/correct/system/header/files.
>
> From what I've read, that should be the default, but that's not the
> behaviour I'm seeing.
>
> Thanks,
> Noel
>
