The appended patch addresses the fact that SBCL_HOME should for all
intents and purposes always end with lib/sbcl, or the contribs won't be
I'm not sure if the actual problem is with the documentation, though, or
in the way SBCL_HOME is used...
RCS file: /cvsroot/sbcl/sbcl/INSTALL,v
retrieving revision 1.14
diff -u -u -r1.14 INSTALL
--- INSTALL 5 Dec 2003 16:56:20 -0000 1.14
+++ INSTALL 27 Mar 2004 16:24:10 -0000
@@ -20,14 +20,15 @@
1. by default, in /usr/lib/sbcl/sbcl.core or /usr/local/lib/sbcl/sbcl.core
2. by environment variable:
- $ export SBCL_HOME=/foo/bar/
+ $ export SBCL_HOME=/foo/bar/lib/sbcl
3. by command line option:
$ sbcl --core /foo/bar/sbcl.core"
The usual, recommended approach is method #1. Method #2 is useful if
-you're installing SBCL on a system in your user account, instead of
-installing SBCL on an entire system. Method #3 is mostly useful for
-testing or other special cases.
+you're installing SBCL on a system in a non-standard location, eg. in
+your user account, instead of installing SBCL on an entire
+system. Method #3 is mostly useful for testing or other special cases.
So: the standard installation procedure is
1. Copy sbcl.core to /usr/lib or /usr/local/lib.
@@ -47,6 +48,9 @@
$ INSTALL_ROOT=/home/me/sbcl sh install.sh
+If your INSTALL_ROOT is XYZ, then you should set SBCL_HOME to
IF YOU HAVE A SOURCE DISTRIBUTION:
Nikodemus Siivola <tsiivola@...> writes:
> The appended patch addresses the fact that SBCL_HOME should for all
> intents and purposes always end with lib/sbcl, or the contribs won't be
Thanks. I've merged this into sbcl-0.8.9.7.
(Incidentally, if anyone knows how I can save just the patch from
messages with the patch inlined, that would be helpful)
http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)
From: Luke Gorrie <luke@bl...> - 2004-03-31 01:54:36
Christophe Rhodes <csr21@...> writes:
> (Incidentally, if anyone knows how I can save just the patch from
> messages with the patch inlined, that would be helpful)
I use `M-x write-region'.
Fancier is `M-x epatch-buffer' to apply the patch directly from the