Bug#474402: sbcl: FTBFS on amd64: mmap: Cannot allocate memory: ensure_space: failed to validate 8589869056 bytes at 0x1000000000

[Kurt Roeckx]

On Sun, Apr 06, 2008 at 06:50:18PM +0100, Thiemo Seufer wrote:
> Kurt Roeckx wrote:
> > On Sat, Apr 05, 2008 at 05:54:55PM +0200, Kurt Roeckx wrote:
> > > 
> > > I've changed the file to 8 GB, a total of 12 GB swap, and that seems
> > > to work so far.
> > 
> > Now it failed with:
> > WARNING! Some of the contrib modules did not build successfully or pass
> > their self-tests. Failed contribs:"
> >   asdf-install
> >   sb-bsd-sockets
> >   sb-posix
> >   sb-simple-streams
> > make: *** [build-arch-stamp] Error 1
> 
> Each of those was caused by:
> 
> [...]
>  unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD "initial thread" {10024C87D1}>:
>    Error during processing of --eval option (LOAD #P"../asdf-stub.lisp"):
> 
>    couldn't fork child process: Cannot allocate memory
> 
> 
> So it look like it is still the same problem.

So I added an additional 8 GB of swap, total of 20 GB swap, and it seems
to build without problems now.

> > Setting up cl-asdf (1.111-1) ...
> > Reinstalling for sbcl
> > Recompiling Common Lisp Controller for sbcl
> > /usr/lib/common-lisp/bin/sbcl.sh loading and dumping clc.
> > STYLE-WARNING: redefining INIT-COMMON-LISP-CONTROLLER-V5 in DEFUN
> > STYLE-WARNING: redefining COMPILE-COMMON-LISP-CONTROLLER-V5 in DEFUN
> > STYLE-WARNING: redefining INIT-COMMON-LISP-CONTROLLER-V4 in DEFUN
> > STYLE-WARNING: redefining INIT-COMMON-LISP-CONTROLLER in DEFUN
> > ; loading system definition from /usr/lib/sbcl/sb-grovel/sb-grovel.asd
> > into
> > ; #<PACKAGE "ASDF1">
> > ; registering #<SYSTEM SB-GROVEL {100262F241}> as SB-GROVEL
> > ;
> > ; compilation unit aborted
> > ;   caught 2 fatal ERROR conditions
> > 
> > Error running init-common-lisp-controller-v4: type component without a name component in NATIVE-NAMESTRING: "lisp"
> > mv: cannot stat `sbcl-new.core': No such file or directory
> > FAILED
> > 
> > Done rebuilding
[...]
> > 
> > I wonder if that's related, and wether I should file a bug for that.
> 
> No idea about this one. It doesn't look like a out-of-memory condition
> to me, and I don't have a amd64 system around to check what's going on.

The only thing I can think of is that sbcl isn't installed only unpacked
at that time.


Kurt