[cl-debian] Bug#431198: gclcvs - FTBFS: Unrecoverable error: invocation history stack overflow.

Package: gclcvs Version: 2.7.0-73 Severity: serious There was an error while trying to autobuild your package:
Automatic build of gclcvs_2.7.0-73 on debian-31.osdl.marist.edu by sbuild/s390 98 [...] cd unixport && echo '(si::use-fast-links nil)(let ((compiler::*speed* 0))(load "boot.lisp"))' | ./saved_pre_gcl && /usr/bin/make saved_gcl && mv saved_gcl saved_pre_gcl GCL (GNU Common Lisp) 2.7.0 CLtL1 profiling Jun 29 2007 12:32:21 Source License: LGPL(gcl,gmp,pargcl), 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/
NIL
;; Loading boot.lisp ;; Compiling ../lsp/gcl_listlib.lsp. Warning: NTH-VALUE is being redefined. ;; End of Pass 1. ;; End of Pass 2. ;; OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=0, (Debug quality ignored) ;; Finished compiling ../lsp/gcl_listlib.o. ;; Loading /build/buildd/gclcvs-2.7.0/lsp/gcl_listlib.o
Unrecoverable error: invocation history stack overflow.
Unrecoverable error: invocation history stack overflow. /bin/sh: line 1: 26687 Done echo '(si::use-fast-links nil)(let ((compiler::*speed* 0))(load "boot.lisp"))' 26688 Aborted | ./saved_pre_gcl make[1]: *** [unixport/saved_pre_gcl] Error 134 make[1]: Leaving directory `/build/buildd/gclcvs-2.7.0' make: *** [build-gprof-stamp] Error 2 ****************************************************************************** Build finished at 20070629-0844 FAILED [dpkg-buildpackage died]

Your message dated Mon, 16 Jul 2007 17:06:56 -0400 with message-id <E1IAXmS-0005hI-N2@intech19.enhanced.com> and subject line gclcvs: FTBFS: ./tmp_image: No such file or directory has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
participants (2)
-
Bastian Blank
-
owner@bugs.debian.org