Anders Magnusson wrote:
> 
> > Like some I would guess who bother to try and build -current, I
> > think I've seen at least one person "hint" at the existing problem
> > that is plaguing -current on NetBSD/vax the past few months.
> >
> [...]
> > make: Could not fork: Cannot allocate memory
> >
> This is because make allocates more memory than DFLDSIZ; currently 16MB.
> If you do "unlimit datasize" before typing make it works better.
> 
> The main problem is that increasing MAXDSIZ to more than currently 24MB
> steals so much memory that the kernel won't boot on low-memory machines.
> If you have much memory in your machine, compile a new kernel with
> "options DFLDSIZ="(48*1024*1024)"
> "options MAXDSIZ="(64*1024*1024)"
> 
> or something similar.

I will try building a kernel with these new limits - thank you!

I had been already pushing both datasize and stacksize to their max
some time ago, as indeed, builds would fail... so I guess the kernel
max limits need to be bumped even higher... yeah, the lifespan of the
VAX has resulted in a really massive range of performance... don't I
know, with 4Mb based VS2000's and then a 64Mb based VS4000/90A  B^)


# limit datasize unlimited
# limit stacksize unlimited
# limit
cputime         unlimited
filesize        unlimited
datasize        24576 kbytes
stacksize       8192 kbytes
coredumpsize    unlimited
memoryuse       57840 kbytes
memorylocked    19280 kbytes
maxproc         148 
openfiles       64 

# make cleandir
cleandir ===> adosfs
cleandir ===> altq
cleandir ===> arch
cleandir ===> arch/vax
cleandir ===> arch/vax/include
cleandir ===> arch/vax/boot
cleandir ===> arch/vax/boot/boot
cleaning the sa library objects
rm -f a.out [Ee]rrs mklog core *.core  
make: Could not fork: Cannot allocate memory

make: stopped in /usr/obj/sys/arch/vax/boot/boot/lib/sa
*** Error code 2

	...