Hello, Stefan.

Just get the latest slime. (The reason of the error is that sys::frame-up-1 function was removed from clisp recently).

-Anton

on Saturday, April 12, 2008, 8:45:50 PM Stefan wrote:

Hi,

When I try to start slime with clisp 2.44.1 or current clisp development-head I get the following protocol:

[1]>> ;; Loading file

/home/Stefan/slime-2.0/swank-loader.lisp ... ;; Loading file /home/Stefan/.slime/fasl/2006-04-20/clisp-2.44-unix-pc386/swank-backend.fas .... /home/Stefan/.slime/fasl/2006-04-20/clisp-2.44-unix-pc386/metering.fas .... .... ;; Loading file /home/Stefan/.slime/fasl/2006-04-20/clisp-2.44-unix-pc386/swank-clisp.fas .... WARNING: Replacing method #<standard-method (#<built-in-class t>)> in #<standard-generic-function call-without-interrupts>

WARNING: Replacing method #<standard-method nil> in #<standard-generic-function lisp-implementation-type-name>

WARNING: Replacing method #<standard-method (#<built-in-class t>)> in #<standard-generic-function set-default-directory>

WARNING: Replacing method #<standard-method (#<built-in-class t>)> in #<standard-generic-function arglist>

** - Continuable Error intern("FRAME-UP-1"): #<package system> is locked If you continue (by typing 'continue'): Ignore the lock and proceed The following restarts are also available: SKIP :R1 skip (load-swank) STOP :R2 stop loading file /cygdrive/D/Eigene_Dateien/development/slime-2.0/swank-loader.lisp ABORT :R3 Abort main loop Break 1 swank-backend[2]>

clisp-2.43 worked without problem.

Why would slime want to tinker with #<built-in-class t> ???

Ignoring the package lock (a clisp feature) does not help. It fails anyway...

Bye, Stefan

  __________________________________________________________

Gesendet von Yahoo! Mail. Der Lieblings-Mailbox der Welt. http://de.overview.mail.yahoo.com _______________________________________________ slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel