Re: [Sbcl-devel] trouble in bootstrapping...

[Christophe R. <cs...@ca...>]

"Perry E. Metzger" <pe...@pi...> writes:

>>> File: /u/perry/src/sbcl/sbcl-build/src/compiler/main.lisp
>>>
>>> In: DEFUN EMIT-MAKE-LOAD-FORM
>>>   (WITH-OUTPUT-TO-STRING (STREAM) (WRITE CONSTANT :STREAM STREAM))
>>> --> LET 
>>> ==>
>>>   (MAKE-STRING-OUTPUT-STREAM :ELEMENT-TYPE 'CHARACTER)
>>> Warning: :ELEMENT-TYPE is not a known argument keyword.
>>
>> Either run the build with an interactive lisp, at which point you will
>> be able to choose the continue restart from the debugger at this
>> point;
>
> Yah, but I wouldn't know what to do there -- if it doesn't support
> :ELEMENT-TYPE it doesn't support it...

True.  But that code path may (I'm not sure, but "may" anyway) never
be called during cross-compilation -- so the build can complete
successfully even if the host compiler is buggy.  On the other hand,
it may not.  Sorry that I can't be more definite :-)

>> patch cmucl before building; or cross-compile from a known-good
>> lisp on a different platform.
>
> I have an old slow Mac running OS X -- I could conceivably try
> bootstrapping from it using SBCL itself. However, INSTALL doesn't
> really explain very well how to handle a cross build, and I have to
> admit I'm pretty unclear on what the process is to do it. :|
>
> Any pointers/explanation you could give me?

As Brian says, the process is more-or-less documented at
sbcl-internals.  I suppose it's not for the faint of heart; does clisp
run on NetBSD?  Clisp 2.33 (absolutely not any earlier versions) has
successfully compiled sbcl on x86/linux.

Cheers,

Christophe
-- 
http://www-jcsu.jesus.cam.ac.uk/~csr21/       +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%")    (pprint #36rJesusCollegeCambridge)