i haven't tried sbcl - is it the preferred lisp for cm and linux these days?

On 8/8/06, Rick Taube <[EMAIL PROTECTED] > wrote:
ive not seen this before. does clisp and or sbcl give you the same
errors??

On Aug 8, 2006, at 8:44 PM, Bill Sack wrote:

> hello rick,
>  i deleted the rt.x86f and .lisp files - then re-compiled cm
>
>  here are the times for the files:
>  [EMAIL PROTECTED] cm]# ls -l bin/cmucl_19c_linux-i686/rt.*
>  -rw-r--r-- 1 root 10766 10240 Aug 8 21:39
> bin/cmucl_19c_linux-i686/rt.x86f
>
> [EMAIL PROTECTED] cm]# ls -l src/rt.*
>  -rw-r--r-- 1 root 10766 1736 Aug 8 21:39 src/rt.lisp
>  -rw-r--r-- 1 32593 10766 1559 Jun 1 03:33 src/rt.scm
>
>  here is the error message while loading cm/slime ['M-x cm' as reg
> user]:
>  Error in function LISP::DO-OLD-RENAME:
>   File "/usr/local/lisp/cm/bin/cmucl_19c_linux-i686/rt.x86f" is not
> writable.
>   [Condition of type SIMPLE-ERROR]
>
>  Restarts:
>   0: [CONTINUE] Try to rename it anyway.
>   1: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL {58BC881D}> on
>   #<CM-SOURCE-FILE "rt" {58BC88C5}>.
>   2: [ACCEPT ] Continue, treating #<ASDF:COMPILE-OP NIL {58BC881D}>
> on
>   #<CM-SOURCE-FILE "rt" {58BC88C5}> as having been
> successful.
>   3: Return NIL from load of
> "/usr/local/lisp/cm/bin/../src/cm.lisp".
>   4: [ABORT ] Skip remaining initializations.
>
>  Debug (type H for help)


Reply via email to