From: Gabriel Dos Reis <gdr@in...> - 2009-07-05 14:25:01
On Sun, Jul 5, 2009 at 7:07 AM, Tobias C. Rittweiler<tcr@...> wrote:
> "Tobias C. Rittweiler" <tcr@...> writes:
>> SB-COLD> Filesystem error with pathname #P"obj/from-host/src/code/cross-early.lisp-obj".
>> 1) the file does not exist, or
>> 2) we are not allow to access the file, or
>> 3) the pathname points to a broken symbolic link.
>> Broken at SI:BYTECODES.No restarts available.
> For some reason the file is called cross-early.FAS not .LISP-OBJ.
I had a fix for this particular failure -- after Juanjo changed the way
ECL handles pathname extension for compile-filename. You need to apply
the following AND use a recent version of ECL (cvs from yesterday for example).
RCS file: /cvsroot/sbcl/sbcl/src/cold/shared.lisp,v
retrieving revision 1.41
diff -p -r1.41 shared.lisp
*** src/cold/shared.lisp 5 May 2009 20:02:12 -0000 1.41
--- src/cold/shared.lisp 5 Jul 2009 14:22:06 -0000
*** 48,53 ****
--- 48,54 ----
#+lispworks ".ufsl" ; as per Lieven Marchand sbcl-devel 2002-02-01
#+(and openmcl (not darwin)) ".pfsl"
#+(and openmcl darwin) ".dfsl"
+ #+ecl ".fas"
;; On most xc hosts, any old extension works, so we use an
;; arbitrary one.
I hope someone will commit it to SBCL.
After that, you will hit another failure -- one with multiple slot problem.
I hope someone here will shed a light about whether it is ECL
bug or SBCL bug.