Comment 2 for bug 356676

Revision history for this message
Colin Watson (cjwatson) wrote :

buildd chroots are torn down when the build finishes, so I don't have that file easily to hand. I tried to reproduce the failure on my laptop and got a completely different error:

  gcl < workxxx
  GCL (GNU Common Lisp) 2.6.7 CLtL1 Dec 6 2008 12:32:21
  Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
  Binary License: GPL due to GPL'ed components: (XGCL READLINE BFD UNEXEC)
  Modifications of this banner must retain notice of a compatible license
  Dedicated to the memory of W. Schelter

  Use (help) to get some basic information on how to use GCL.
  Temporary directory for compiler files set to /tmp/

  >
  Loading init.lisp
  Loading acl2r.lisp
  Finished loading acl2r.lisp
  Loading acl2-init.lisp
  Loading acl2.lisp

  Error: Caught fatal error [memory may be damaged]
  Fast links are on: do (si::use-fast-links nil) for debugging
  Error signalled by LOAD.
  Broken at LOAD. Type :H for Help.
  ACL2>>
  Error: The function COMPILE-ACL2 is undefined.
  Fast links are on: do (si::use-fast-links nil) for debugging
  Error signalled by LISP:EVALHOOK.
  Backtrace: system:universal-error-handler > LISP:EVALHOOK

  Broken at LOAD.
  ACL2>>
  Error: The function EXIT-LISP is undefined.
  Fast links are on: do (si::use-fast-links nil) for debugging
  Error signalled by LISP:EVALHOOK.
  Backtrace: system:universal-error-handler > LISP:EVALHOOK

  Broken at LOAD.
  ACL2>>make[1]: *** [full] Error 255
  make[1]: Leaving directory `/home/cjwatson/src/ubuntu/acl2/acl2-3.4'
  make: *** [saved_acl2] Error 2
  dpkg-buildpackage: failure: debian/rules build gave error exit status 2

Sorry I apparently can't help here. Maybe you can reproduce this in a chroot if you want to hack on it and don't have a jaunty system to hand? pbuilder should be adequate.