Hello, apparently Lispworks is not among the implementations which work out-of-the-box with Debian's common-lisp-controller (at least on etch/testing which I tried). Does it run on later versions, or does anybody here have patches for making it work? Thank you, Nicolas
Hi, Debian user
It's not a problem of common-lisp-controller but asdf. I suggest
follow steps:
1. Make a dir: /var/cache/common-lisp-controller/0/lispworks, and make
sure you lispworks user (the user which will run lispworks binary) can
write to this directory.
2. Put two line in ~/.lispworks or a build script for save-image:
(load "/usr/share/common-lisp/source/common-lisp-controller/common-
lisp-controller.lisp")
(common-lisp-controller:init-common-lisp-controller-v4 "lispworks")
3. Patch this file: /usr/share/common-lisp/source/asdf/asdf.lisp
=
=
=
=
=
=
========================================================================
--- asdf.lisp.orig 2008-03-05 23:55:19.000000000 +0800
+++ asdf.lisp 2008-03-05 23:59:46.000000000 +0800
@@ -1188,6 +1188,8 @@
(system:call-system-showing-output
command
:shell-type "/bin/sh"
+ :prefix ""
+ :show-cmd nil
:output-stream *verbose-out*)
#+clisp ;XXX not exactly *verbose-out*, I know
=
=
=
=
=
=
========================================================================
4. save a new image with clc included, or just start lispworks directly.
>
> Hello,
>
> apparently Lispworks is not among the implementations which work
> out-of-the-box with Debian's common-lisp-controller (at least on
> etch/testing which I tried). Does it run on later versions, or does
> anybody here have patches for making it work?
>
> Thank you,
> Nicolas
>