Is anyone seeing this? With current 4.1 sources, on a machine with "only" 1GB of main memory + 1GB swap, the following part of `make install`
Adding java source files from srcdir '/cvs/gcc/trunk/libjava/classpath'. Adding java source files from VM directory /cvs/gcc/trunk/libjava /tmp/OBJ-1203-1719/i686-pc-linux-gnu/libjava Adding generated files in builddir '..'. make -f /cvs/gcc/trunk/libjava/classpath/lib/Makefile.gcj \ GCJ='/tmp/OBJ-1203-1719/gcc/gcj \ -B/tmp/OBJ-1203-1719/i686-pc-linux-gnu/libjava/ \ -B/tmp/OBJ-1203-1719/gcc/' \ compile_classpath='..:/cvs/gcc/trunk/libjava:/tmp/OBJ-1203-1719/i686-pc-linux-gnu/libjava:/cvs/gcc/trunk/libjava/classpath:/cvs/gcc/trunk/libjava/classpath/external/w3c_dom:/cvs/gcc/trunk/libjava/classpath/external/sax:.:' \ top_srcdir=/cvs/gcc/trunk/libjava/classpath spawns a recursive make (GNU make 3.80) that consumes some 450MB of memory and triggers a system load of 12+, basically rendering the machine dead for about a minute. On a different machine with only 512MB + 1GB swap, this time running FreeBSD 5.3, I cannot install GCC any longer. This seems to be a regression between the 20051125 and 20051202 snapshots of GCC 4.1, but I failed to find any indications in the Makefiles, so the problem may a bit older. Any ideas how I could nail this down? Anyone else seeing this? Gerald
