Package: stumpwm
Version: 0.0.4+cvs20050802-1
Severity: grave
Justification: renders package unusable

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

stumpwm requires the CLX components, which is not installed by
default, but only recommended.

While once I have installed cmucl-source, I can successfully compile
stumpwm with cmucl, I get a series of warning trying to compile it
with sbcl + cl-clx-sbcl (with or without cmucl-source). Even if this
should be another bug, it's always CLX-relevant, so I'm posting
here (I can file a distinct bug after your request, if needed).

=====
; compiling (DEFTYPE ANGLE ...)
; compiling (DEFUN ANGLEP ...)
; compiling (DECLAIM (INLINE CHAR->CARD8 ...))
; compiling (CHAR-TRANSLATORS)
; compiling (DEFUN MAKE-PROCESS-LOCK ...)
; compiling (DEFMACRO HOLDING-LOCK ...)
; compiling (DEFMACRO WITHOUT-ABORTS ...)
; compiling (DECLAIM (INLINE YIELD))
; compiling (DEFUN YIELD ...)
; compiling (DEFUN PROCESS-BLOCK ...)
; compiling (DECLAIM (INLINE PROCESS-WAKEUP))
; compiling (DEFUN PROCESS-WAKEUP ...)
; compiling (DECLAIM (INLINE CURRENT-PROCESS))compilation aborted
because of fatal error:
                READ failure in
                COMPILE-FILE:
                READER-ERROR at
                37799 (line 1285,
                column 30) on
                #<SB-SYS:FD-STREAM
                for "file
                /usr/share/common-lisp/source/clx/dependent.lisp"
                                                  {9D6C111}>:
Symbol "CURRENT-THREAD-ID" not found in the SB-THREAD package.

; /var/cache/common-lisp-controller/luca/sbcl/clx/dependent.fasl
  written
; compilation finished in 0:00:00

debugger invoked on a ASDF:COMPILE-WARNED in thread #<THREAD "initial
thread" {9003291}>:
  erred while invoking #<COMPILE-OP NIL {917D1A9}> on
  #<CLX-SOURCE-FILE "dependent" {90C5021}>

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

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL {917D1A9}> on
              #<CLX-SYSTEM::CLX-SOURCE-FILE "dependent" {90C5021}>.
  1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {917D1A9}> on
              #<CLX-SYSTEM::CLX-SOURCE-FILE "dependent" {90C5021}> as
  having
              been successful.
  2: [ABORT ] Exit debugger, returning to top level.

((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP
ASDF:CL-SOURCE-FILE))
 #<unavailable argument>
 #<unavailable argument>
 #<ASDF:COMPILE-OP NIL {917D1A9}>
 #<CLX-SYSTEM::CLX-SOURCE-FILE "dependent" {90C5021}>)
0] 
=====

- From the README, it seems that the author tested it with SBCL as well
as with CMUCL (the CL implementation he used), so it should work with
sbcl as well. But I'm not a so deeply CL-good user to solve the error
above, sorry.

If we can get stumpwm working with sbcl, IMHO the best thing should be
adding the following dependecy: cl-clx-sbcl | cmucl-source. But in
that case, we can have a situation like this: sbcl + cmucl-source +
stumpwm (which doesn't work).

So, probably (but I'm not sure) the sbcl support could be dropped out
in favor of a unique cmucl support.

Am I right?

Thx, bye,
Gismo / Luca

- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-rc6
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages stumpwm depends on:
ii  cl-port                       20050624-2 Common Lisp Object Collections Por
ii  common-lisp-controller        4.16       This is a Common Lisp source and c

Versions of packages stumpwm recommends:
pn  cl-clx-sbcl | cmucl-source    <none>     (no description available)

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDBbbHVAp7Xm10JmkRAufNAKCKxoYOWee2Cinmo8U7WEM9e9GmtACfcDkP
QyACHP9mFEtvBsx2HhTg1p0=
=4Mf0
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to