Bug#568818: Not sure that the cl-swank problem is fixed?

A.J. Rossini blindglobe at gmail.com
Tue Mar 9 19:54:00 UTC 2010


On Tue, Mar 9, 2010 at 9:39 AM, Milan Zamazal <pdm at debian.org> wrote:
> I believe this problem has been fixed in cl-swank 20100220-4 uploaded
> just a while ago.  When it appears in the archive, please test it.

It fixes the reported problem, and introduces another --- which isn't
CLC's fault anymore, but a SLIME/SBCL interaction (verified since
CMUCL and CLISP work, and SLIME/ECL reports that I need to upgrade
from 9.x to 10.x...)

(so I'm running this on an EEEPC netbook, so I'm i686 and not AMD
arch, so I'm a bit behind SBCL-wise).

Starting SLIME with SBCL gives me:


(progn (load "/usr/share/common-lisp/source/slime/swank-loader.lisp"
:verbose t) (funcall (read-from-string "swank-loader:init")) (funcall
(read-from-string "swank:start-server") "/tmp/slime.10621"
:coding-system "iso-latin-1-unix"))

This is SBCL 1.0.31.0.debian, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
*
; loading #P"/usr/share/common-lisp/source/slime/swank-loader.lisp"
; loading #P"/var/cache/common-lisp-controller/1000/SBCL/usr/share/common-lisp/source/slime/swank/fasl/sbcl-1.0.31.0.debian-linux-x86/swank-backend.fasl"
; loading #P"/var/cache/common-lisp-controller/1000/SBCL/usr/share/common-lisp/source/slime/swank/fasl/sbcl-1.0.31.0.debian-linux-x86/swank-source-path-parser.fasl"
; loading #P"/var/cache/common-lisp-controller/1000/SBCL/usr/share/common-lisp/source/slime/swank/fasl/sbcl-1.0.31.0.debian-linux-x86/swank-source-file-cache.fasl"

; compiling file "/usr/share/common-lisp/source/slime/swank-sbcl.lisp"
(written 20 FEB 2010 08:15:18 PM):
;
; compilation unit aborted
;   caught 1 fatal ERROR condition
; compilation aborted after 0:00:54.488
;;
;; Error while compiling /usr/share/common-lisp/source/slime/swank-sbcl.lisp:
;;   don't recognize component type COMPILED-FILE
;; Aborting.
;; *


SO...  at this point, I M-x slime-abort-connection  and check a bit
and manually load within *inferior-lisp*

(load "/usr/share/common-lisp/source/slime/swank-sbcl.lisp")

; loading system definition from /usr/lib/sbcl/sb-grovel/sb-grovel.asd into
; #<PACKAGE "ASDF1">
; registering #<SYSTEM SB-GROVEL {AD88C59}> as SB-GROVEL


debugger invoked on a SB-C::INPUT-ERROR-IN-COMPILE-FILE in thread
#<THREAD "initial thread" RUNNING {AA53789}>:
  READ failure in COMPILE-FILE:
    SB-INT:SIMPLE-READER-PACKAGE-ERROR at 2176 (line 75, column 41) on
#<SB-SYS:FD-STREAM for "file
/usr/share/common-lisp/source/slime/swank-sbcl.lisp" {AFA3D51}>:
      package "SB-BSD-SOCKETS" not found

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT] Exit debugger, returning to top level.

(SB-C::READ-FOR-COMPILE-FILE
 #<SB-SYS:FD-STREAM for "file
/usr/share/common-lisp/source/slime/swank-sbcl.lisp" {AFA3D51}>
 2102)
0]



and note that (list-all-packages)   shows many packages, but
SB-BSD-SOCKETS isn't one of them.  However, thanks to having
SBCL-source installed, I see that it could be there since it's
installed with the source install.

I think this is an SBCL issue, and I've got some bug reports to
consider filing in the right places.  Again, thanks to all for your
support, help, and assistance (and more importantly, for simply
reading this bug report).

best,
-tony

blindglobe at gmail.com
Muttenz, Switzerland.
"Commit early,commit often, and commit in a repository from which we
can easily roll-back your mistakes" (AJR, 4Jan05).

Drink Coffee:  Do stupid things faster with more energy!





More information about the pkg-common-lisp-devel mailing list