Hi all,

I tried a compilation of GCC 3.3 (20030324 snapshot) for VAX on my 4000/200 but
it died somewhere in the middle.  I know I'm a masochist for compiling GCC on
such a slow machine, but I don't belive in cross-builds.  Anyway, here's what
happens.

It gets all the way through stage1 and stage2, and then moves on to the
libraries.  Then in libstdc++-v3 it stops:

gmake[2]: Entering directory
`/usr/src/gcc-20030324/vax-unknown-netbsdelf1.6.1./libstdc++-v3/testsuite'
`echo /usr/src/gcc-20030324/gcc/xgcc -shared-libgcc -B/usr/src/gcc-20030324/gcc/
-nostdinc++ 
-L/usr/src/gcc-20030324/vax-unknown-netbsdelf1.6.1./libstdc++-v3/src
-L/usr/src/gcc-20030324/vax-unknown-netbsdelf1.6.1./libstdc++-v3/src/.libs
-B/usr/gcc/vax-unknown-netbsdelf1.6.1./bin/
-B/usr/gcc/vax-unknown-netbsdelf1.6.1./lib/ -isystem
/usr/gcc/vax-unknown-netbsdelf1.6.1./include  | sed 's/xgcc/g++/g'`
-DHAVE_CONFIG_H -I. -I. -I.. -nostdinc++
-I/usr/src/gcc-20030324/vax-unknown-netbsdelf1.6.1./libstdc++-v3/include/vax-unknown-netbsdelf1.6.1.
-I/usr/src/gcc-20030324/vax-unknown-netbsdelf1.6.1./libstdc++-v3/include
-I../libsupc++      -g -O2 -c abi_check.cc
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.


I would submit a bug report but I really don't know why or how g++ is dying.  I
figured the people doing gcc work on VAXen are all on this list.  Is it possible
that it's running out of memory, or would that be a different error?  I have
32MB physical plus another 32MB swap, which should be more than enough for a
CISC system like this.

Thanks in advance for any help anyone is able to provide.

-- 
Henry Bent
hbent@cs.oberlin.edu