[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

PCL problems

Hi,

Thanks for the previous responses.

I am still having trouble with getting PCL up on KCL.  Here is the
configuration information that I forgot to include in my last
message...

Running KCL (June 3, '87) on a Sun 3/50 with a file server (Sun
3/260?).  
SUN OS 4.0.3 
cc 1.103 (This is what I guess that PCL is
using, is there a way to change that to use gcc?  We have the latest
version.)

The machines only have 4 meg of RAM, and 10 meg of swap.  (There are
some color machines with 8 meg RAM and 30 meg swap, but I haven't been using
those.)

I added the call to 
	(si:catch-bad-signals) 
before starting the compile of PCL, and I now get the following error
message (which is much better than just a segmentation fault, although
I don't know what signal 11 means).  Any new suggestions are welcomed.

Joseph
(jrobinso@polyslo.calpoly.edu)
---------------------------------------------------------------------

Compiling /blackbird/home/clos/pcl_src/fixup.lisp.

Error: Signal 11 caught.
       The internal memory may be broken.
       You should check the signal and exit from Lisp.
Error signalled by FIX-EARLY-GENERIC-FUNCTIONS.
Backtrace:  > eval > FIX-EARLY-GENERIC-FUNCTIONS
; (FIX-EARLY-GENERIC-FUNCTIONS) is being compiled.
;;; The form (FIX-EARLY-GENERIC-FUNCTIONS) was not evaluated successfully.
;;; You are recommended to compile again.
Successfully called fix-early-generic-functions.

No FASL generated.
Loading binary of FIXUP...
Error: Cannot open the file /blackbird/home/clos/pcl_bin/fixup.o.
Error signalled by LOAD.

Broken at LOAD.  Type :H for Help.
>>