Hi,
I've been running Emacs/Slime/OpenMCL on Mac OS X Tiger (PPC) for several months now with no problem. I just updated and rebuilt OpenMCL (via (ccl:rebuild-ccl :force t)), and now when starting slime, I get the following error. I then updated Slime with the current CVS, but am still getting the error.
Does anyone have an idea as to what is going wrong?
Thanks, Chris Van Dusen.
(progn (load "/Users/chrisvandusen/bin/slime/slime/swank- loader.lisp" :verbose t) (funcall (read-from-string "swank:start- server") "/tmp/slime.521" :coding-system "iso-latin-1-unix"))
; loading system definition from /Users/chrisvandusen/.asdf-install- dir/systems/asdf-install.asd into #<Package "ASDF0"> ; registering #<SYSTEM ASDF-INSTALL #x85B21D6> as ASDF-INSTALL Welcome to OpenMCL Version 1.1-r7706 (DarwinPPC32)! ? ;Loading #P"/Users/chrisvandusen/bin/slime/slime/swank-loader.lisp"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank-backend.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank-backend.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/nregex.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/nregex.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/metering.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/metering.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank-openmcl.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank-openmcl.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank-gray.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank-gray.dfsl"... ;Compiling "/Users/chrisvandusen/bin/slime/slime/swank.lisp"... ;Loading #P"/Users/chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1- darwin-powerpc/swank.dfsl"...;;
;; Error while loading: /Users/ chrisvandusen/.slime/fasl/2007-11-23/openmcl-1.1-darwin-powerpc/ swank.dfsl
;; Condition: Package name "SWANK-IO- PACKAGE" is already in use.
;; Aborting.
;; ?
Chris Van Dusen cavandusen@gmail.com wrote:
Hi,
I've been running Emacs/Slime/OpenMCL on Mac OS X Tiger (PPC) for several months now with no problem. I just updated and rebuilt OpenMCL (via (ccl:rebuild-ccl :force t)), and now when starting slime, I get the following error. I then updated Slime with the current CVS, but am still getting the error.
Nobody seems to have replied, but I just got this error, trying CCL on Mac OS X Leopard yesterday for the first time (fresh slime from CVS).
Did you eventually understand what was wrong ?
* Didier Verna [2008-01-21 23:40+0100] writes:
Chris Van Dusen cavandusen@gmail.com wrote:
Hi,
I've been running Emacs/Slime/OpenMCL on Mac OS X Tiger (PPC) for several months now with no problem. I just updated and rebuilt OpenMCL (via (ccl:rebuild-ccl :force t)), and now when starting slime, I get the following error. I then updated Slime with the current CVS, but am still getting the error.
Nobody seems to have replied, but I just got this error, trying CCL on Mac OS X Leopard yesterday for the first time (fresh slime from CVS).
Did you eventually understand what was wrong ?
I can't answer this question (I don't have a machine to run CCL), but there were some messages on the OpenMCL mailing list which might be related: http://thread.gmane.org/gmane.lisp.openmcl.devel/1898/focus=1902
All those ? in the error message could also be caused by some character encoding problem. There are some forms in swank-openmcl.lisp with #+openmcl-unicode-strings, maybe those need be updated.
Helmut.
Helmut Eller heller@common-lisp.net wrote:
I can't answer this question (I don't have a machine to run CCL), but there were some messages on the OpenMCL mailing list which might be related: http://thread.gmane.org/gmane.lisp.openmcl.devel/1898/focus=1902
All those ? in the error message could also be caused by some character encoding problem. There are some forms in swank-openmcl.lisp with #+openmcl-unicode-strings, maybe those need be updated.
Actually, the problem was just building a new CCL from within Slime, in which case some Slime packages were included in the image. Next time you run Slime with CCL, you get a conflict.
-
Chris Van Dusen -
Didier Verna -
Helmut Eller