From: Josh E. <jo...@el...> - 2009-11-13 20:21:19
|
On Thu, Nov 12, 2009 at 07:15:38PM -0800, Jeff Cunningham wrote: > > I would be willing to do that this new account I'm trying to work on > > if it will manage it and I can work through all the kinks. The first > > one I've run into is the amount of memory it seems to want to build > > it. It complained immediately that > > > > RUNTIME WARNING: data size resource limit may be too low, > > try decreasing the dynamic space size with --dynamic-space-size > > mmap: Cannot allocate memory > > ensure_space: failed to validate 419430400 bytes at 0x4c000000 > > (hint: Try "ulimit -a"; maybe you should increase memory limits.) > > > > The ulimit -a for this account gives me: > > > > -bash-3.2$ ulimit -a > > core file size (blocks, -c) unlimited > > data seg size (kbytes, -d) 204800 > > file size (blocks, -f) unlimited > > max locked memory (kbytes, -l) 16384 > > max memory size (kbytes, -m) 98304 > > open files (-n) 128 > > pipe size (512 bytes, -p) 1 > > stack size (kbytes, -s) 8192 > > cpu time (seconds, -t) unlimited > > max user processes (-u) 64 > > virtual memory (kbytes, -v) 212992 > > > > Looks like I need about 20x the memory I'm allocated to build it with. > > Is there a way to get around this? Yes, decrease the dynamic space size. Lowering it to 150MB should let you run under those resource limits: sbcl --dynamic-space-size 150 |