Hi!
I'm trying to build sbcl 0.9.5 and later 0.9.6
on x86_64 system.
First, I downloaded and installed x86_64 sbcl 0.9.5
from SuSE 9.X (can't remember precisely SuSE version)
to use as build host system. Unfortunately build
process with this sbcl 0.9.5 crashes almost instantly
on compiling show.lisp:
================================================
...
; compiling file "/home/vadim/test/sbcl-0.9.6/src/code/show.lisp"
(written 14 JUL 2005 08:30:38 PM):
; compiling (IN-PACKAGE "SB!INT")
; compiling (DEFUN CANNOT-/SHOW ...)
; file: /home/vadim/test/sbcl-0.9.6/src/code/show.lisp
; in: DEFUN CANNOT-/SHOW
; (VALUES)
;
; note: deleting unreachable code
; compiling (DEFMACRO /SHOW ...)
; compiling (DEFMACRO /NOSHOW ...)
; compiling (DEFMACRO /XHOW ...)
; compiling (DEFMACRO /NOXHOW ...)
; compiling (DEFMACRO /SHOW0 ...)make-host-1.sh: line 60: 7140
Trace/breakpoint trap $SBCL_XC_HOST <<-'EOF'
;; (We want to have some limit on print length and print level
;; during bootstrapping because PRINT-OBJECT only gets set
;; up rather late, and running without PRINT-OBJECT it's easy
;; to fall into printing enormous (or infinitely circular)
...
...
================================================
Second I've tried to use clisp 2.35 which I build
from sources. In this case make.sh runs for almost
40 minutes but once again crashes shortly after
first start of freshly build sbcl 0.9.6:
================================================
//entering make-target-2.sh
//doing warm init
This is SBCL 0.9.6, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
*
10
*
5
*
T
*
; compiling file "/home/vadim/test/sbcl-0.9.6/src/pcl/early-low.lisp"
(written 21 SEP 2005 07:01:14 PM):
; compiling (IN-PACKAGE "SB-PCL")
; compiling (/SHOW "starting early-low.lisp")
; compiling (DEFVAR *PCL-PACKAGE* ...)
; compiling (DEFUN STRUCTURE-TYPE-P ...)
; compiling (DEFUN FORMAT-SYMBOL ...)
; compiling (DEFUN MAKE-CLASS-SYMBOL ...)
; compiling (DEFUN MAKE-WRAPPER-SYMBOL ...)
; compiling (DEFUN CONDITION-TYPE-P ...)
; compiling (DECLAIM (SPECIAL *THE-CLASS-T* ...))
; compiling (DECLAIM (SPECIAL *THE-WRAPPER-OF-T* ...))
; compiling (/SHOW "finished with early-low.lisp")
; SYS:SRC;PCL;EARLY-LOW.FASL.NEWEST written
; compilation finished in 0:00:00
; compiling file "/home/vadim/test/sbcl-0.9.6/src/pcl/macros.lisp"
(written 14 JUL 2005 11:45:42 PM):
; compiling (IN-PACKAGE "SB-PCL")
; compiling (/SHOW "starting pcl/macros.lisp")
; compiling (DECLAIM (DECLARATION %METHOD-NAME ...))
; compiling (/SHOW "done with DECLAIM DECLARATION")
; compiling (DEFUN GET-DECLARATION ...)
; compiling (/SHOW "pcl/macros.lisp 85")
; compiling (DEFMACRO DOPLIST ...)
; compiling (/SHOW "pcl/macros.lisp 101")
; compiling (DEFMACRO DOLIST-CAREFULLY ...)
; compiling (/SHOW "pcl/macros.lisp 119")
; compiling (DEFVAR *FIND-CLASS* ...)
; compiling (DEFMACRO FIND-CLASS-CELL-CLASS ...)
; compiling (DEFMACRO FIND-CLASS-CELL-PREDICATE ...)
; compiling (DEFMACRO MAKE-FIND-CLASS-CELL ...)
; compiling (DEFUN FIND-CLASS-CELL ...)
; compiling (/SHOW "pcl/macros.lisp 157")
; compiling (DEFVAR
*CREATE-CLASSES-FROM-INTERNAL-STRUCTURE-DEFINITIONS-P* ...)
; compiling (DEFUN FIND-CLASS-FROM-CELL ...)fatal error encountered in
SBCL pid 7579:
no pointer at 0 in hash table
The system is too badly corrupted or confused to continue at the Lisp
level. If the system had been compiled with the SB-LDB feature, we'd
drop into the LDB low-level debugger now. But there's no LDB in this
build, so we can't really do anything but just exit, sorry.
================================================
Нardware: Athlon 64 3200+ on ASUS A8V Deluxe with 1Gb RAM.
Software: ALT Linux with heavily patched 2.6.12 x86_64
kernel.
My primary suspect for trouble maker is kernel,
more precise some kernel patches which may be incompatible
with sbcl. On the other hand I have no any troubles on the
same system with precisely the same kernel but built
for 32-bit i586.
Any ideas?
Best wishes,
Vadim
--
Vadim V. Zhytnikov
<vvzhy@...>
<vvzhy@...>
|