Tim Rightnour wrote:
> So I tried to kick off a build.sh tools on one of my prep machines today, and
> it exploded.  This machine has 64MB of ram, and 256MB of swap.  It's running
> full -current as of about 1 week ago.
> 
> cc   -O -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros
> -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H
> -DGENERATOR_FILE  -o build/genattrtab \
>  build/genattrtab.o build/genautomata.o \
>  build/rtl.o build/read-rtl.o build/ggc-none.o build/min-insn-modes.o
> build/gensupport.o build/insn-conditions.o build/print-rtl.o build/errors.o \
>  build/varray.o ../build-powerpc-unknown-netbsd3.99.22/libiberty/libiberty.a -lm
> build/genattrtab
> /usr/src/tools/gcc/../../gnu/dist/gcc4/gcc/config/rs6000/rs6000.md >
> tmp-attrtab.c
> 
> out of memory allocating 250000 bytes after a total of 134102464 bytes
> nbgmake[1]: *** [s-attrtab] Error 1
> nbgmake[1]: Leaving directory `/obj/tools/gcc/build/gcc'
> nbgmake: *** [all-gcc] Error 2
> 
> *** Failed target:  .build_done
> 
> Is that not enough ram to build gcc anymore?  It seems a bit excessive.

Nope.  Not enough. :(

need a datasize of 256MB for gcc these days.