First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
So I'm on Ubuntu 10.04 and I've successfully installed Clisp and SBCL. Clisp was apt-getted; SBCL was installed from latest Linuxx86 "binaries." Both work in terminals. Clisp actually works with Slime, but SBCL not. This is what Slime starting with SBCL gives:
------------------- 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"
debugger invoked on a SB-C::INPUT-ERROR-IN-COMPILE-FILE in thread #<THREAD "initial thread" RUNNING
{A9F28C9}>: READ failure in COMPILE-FILE: SB-INT:SIMPLE-READER-PACKAGE-ERROR at 5151 (line 128, column 45) on #<SB-SYS:FD-STREAM
for "file /usr/share/common-lisp/source/slime/swank-loader.lisp"
{A9FC3D1}>: package "CLC" 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-loader.lisp" {A9FC3D1}> 4663) 0] -------------------------
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
Olwe
On 05/23/2010 09:19 AM, Olwe Melwasul wrote:
First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
So I'm on Ubuntu 10.04 and I've successfully installed Clisp and SBCL. Clisp was apt-getted; SBCL was installed from latest Linuxx86 "binaries." Both work in terminals. Clisp actually works with Slime, but SBCL not. This is what Slime starting with SBCL gives:
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"
debugger invoked on a SB-C::INPUT-ERROR-IN-COMPILE-FILE in thread #<THREAD �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �"initial thread" RUNNING �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �{A9F28C9}>: ��READ failure in COMPILE-FILE: �� �SB-INT:SIMPLE-READER-PACKAGE-ERROR at 5151 (line 128, column 45) on #<SB-SYS:FD-STREAM �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �for "file /usr/share/common-lisp/source/slime/swank-loader.lisp" �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �{A9FC3D1}>: �� � �package "CLC" 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-loader.lisp" {A9FC3D1}> �4663) 0]
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
Olwe
The very first suggestion is to add this line to your .emacs file:
(setq inferior-lisp-program "/usr/bin/sbcl")
Change the path to suit.
Carlos
On 05/23/2010 09:19 AM, Olwe Melwasul wrote:
First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
So I'm on Ubuntu 10.04 and I've successfully installed Clisp and SBCL. Clisp was apt-getted; SBCL was installed from latest Linuxx86 "binaries." Both work in terminals. Clisp actually works with Slime, but SBCL not. This is what Slime starting with SBCL gives:
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"
debugger invoked on a SB-C::INPUT-ERROR-IN-COMPILE-FILE in thread #<THREAD �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �"initial thread" RUNNING �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �{A9F28C9}>: ��READ failure in COMPILE-FILE: �� �SB-INT:SIMPLE-READER-PACKAGE-ERROR at 5151 (line 128, column 45) on #<SB-SYS:FD-STREAM �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �for "file /usr/share/common-lisp/source/slime/swank-loader.lisp" �� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �{A9FC3D1}>: �� � �package "CLC" 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-loader.lisp" {A9FC3D1}> �4663) 0]
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
Olwe
Something else occurs to me re: ASDF in SBCL. If you installed SBCL manually, then you probably don't have a nice /etc/sbclrc file. Here's what Gentoo does for you when you install SBCL from Portage. Notice how it loads ASDF:
(setf (logical-pathname-translations "SYS") '(("SYS:SRC;**;*.*.*" #p"/usr/lib64/sbcl/src/**/*.*") ("SYS:CONTRIB;**;*.*.*" #p"/usr/lib64/sbcl/**/*.*")))
(in-package #:cl-user)
#+(or sbcl ecl allegro) (require :asdf) #-(or sbcl ecl allegro) (let ((*compile-print* nil) (*compile-verbose* nil) #+cmu (ext:*gc-verbose* nil)) (handler-bind ((warning #'muffle-warning)) (load #p"/usr/share/common-lisp/source/asdf/asdf.lisp" :print nil :verbose nil)))
(push #p"/usr/share/common-lisp/systems/" asdf:*central-registry*)
(let ((*compile-print* nil) (*compile-verbose* nil) #+cmu (ext:*gc-verbose* nil)) (handler-bind ((warning #'muffle-warning)) (asdf:oos 'asdf:load-op :asdf-binary-locations))) (setf asdf:*centralize-lisp-binaries* t)
Carlos
On Sunday 23 May 2010 19:19:05, Olwe Melwasul wrote:
First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
It's probably better to ask on sbcl-help list.
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
The error message is about the CLC package which is the Debian's common-lisp- controller (some sort of infrastructure that is now mostly obsoleted). It looks like that SLIME in Debian/Ubuntu is set up to use CLC and SBCL doesn't know how to load it (because probably Debian's SBCL packages also install configuration files). But you probably don't need CLC, so you can just install vanilla version of SLIME instead of the one provided in repository.
---- Кальянов Дмитрий
On Sun, May 23, 2010 at 2:00 PM, Kalyanov Dmitry kalyanov.dmitry@gmail.com wrote:
On Sunday 23 May 2010 19:19:05, Olwe Melwasul wrote:
First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
It's probably better to ask on sbcl-help list.
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
The error message is about the CLC package which is the Debian's common-lisp- controller (some sort of infrastructure that is now mostly obsoleted). It looks like that SLIME in Debian/Ubuntu is set up to use CLC and SBCL doesn't know how to load it (because probably Debian's SBCL packages also install configuration files). But you probably don't need CLC, so you can just install vanilla version of SLIME instead of the one provided in repository.
Кальянов Дмитрий
Obsolete? Why do you say that? Version 7.2 is in unstable http://packages.debian.org/search?keywords=common-lisp-controller. It seems very much alive to me.
Indeed the problem originally reported is that the sbcl is not clc-ized, having come from an external source, whereas other lisp tools (like slime) are coming from the repository. You can check my blog http://lhealy.livejournal.com/11629.html showing how I clc-ized CCL, and look at the links there to the "Common Lisp in Debian" manual.
Liam
On 05/23/2010 02:08 PM, Liam Healy wrote:
On Sun, May 23, 2010 at 2:00 PM, Kalyanov Dmitry kalyanov.dmitry@gmail.com wrote:
On Sunday 23 May 2010 19:19:05, Olwe Melwasul wrote:
First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
It's probably better to ask on sbcl-help list.
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
The error message is about the CLC package which is the Debian's common-lisp- controller (some sort of infrastructure that is now mostly obsoleted). It looks like that SLIME in Debian/Ubuntu is set up to use CLC and SBCL doesn't know how to load it (because probably Debian's SBCL packages also install configuration files). But you probably don't need CLC, so you can just install vanilla version of SLIME instead of the one provided in repository.
Кальянов Дмитрий
Obsolete? Why do you say that? Version 7.2 is in unstable http://packages.debian.org/search?keywords=common-lisp-controller. It seems very much alive to me.
Indeed the problem originally reported is that the sbcl is not clc-ized, having come from an external source, whereas other lisp tools (like slime) are coming from the repository. You can check my blog http://lhealy.livejournal.com/11629.html showing how I clc-ized CCL, and look at the links there to the "Common Lisp in Debian" manual.
Liam
Gentoo used to use common-lisp-controller. They copied the lisp configuration from debian. But now if you use the gentoo lisp overlay (as you must if you want any lisp packages that are remotely up to date), you will find that support for it has been removed. Then you have to install a couple other packages that take over some of what common-lisp-controller does:
cl-asdf dev-lisp/cl-asdf-binary-locations
Of course you don't worry about it because they are pulled in as dependencies as soon as you try to emerge any ASDF package. But perhaps common-lisp-controller is optional in debian? The CLiki page seems to hint at this:
http://www.cliki.net/common-lisp-controller
So by all means use the SBCL package from the Ubuntu repository, and make sure clc is installed as well. You'll get a nice /etc/sbclrc (or equivalent) config file for free. And, if debian is is cool as gentoo, all your .fasl files will go into ~/.fasls/, which makes them easy to clean.
Carlos
* Olwe Melwasul [2010-05-23 17:19+0200] writes:
First post here. I'm a newbie to all things lisp. Hopefully this is the place to ask...
Please post plain text messages on this list.
So I'm on Ubuntu 10.04 and I've successfully installed Clisp and SBCL. Clisp was apt-getted; SBCL was installed from latest Linuxx86 "binaries." Both work in terminals. Clisp actually works with Slime, but SBCL not. This is what Slime starting with SBCL gives:
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"
debugger invoked on a SB-C::INPUT-ERROR-IN-COMPILE-FILE in thread #<THREAD "initial thread" RUNNING
{A9F28C9}>: READ failure in COMPILE-FILE: SB-INT:SIMPLE-READER-PACKAGE-ERROR at 5151 (line 128, column 45) on #<SB-SYS:FD-STREAM
for "file /usr/share/common-lisp/source/slime/swank-loader.lisp"
{A9FC3D1}>: package "CLC" 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-loader.lisp" {A9FC3D1}> 4663) 0]
Alas, the limbo between hand-installed and apt-get wizardry therein I am no doubt lost. Actually, my Emacs (23.1.1), my Slime (1:20090908-1 according to Synaptic) and Clisp were all apt-got. Can this be sorted out? Or must I blitz my hard drive, install NetBSD, Stump, and everything Lisp from source?
The Ubuntu/Debian Slime package is broken; they patched swank-loader.lisp and introduced the problem. Send a bug report to the Ubuntu/Debian lisp maintainers.
Helmut
-
Carlos Konstanski -
Helmut Eller -
Kalyanov Dmitry -
Liam Healy -
Olwe Melwasul