On Sun, Oct 19, 2008 at 4:07 PM, Robert Ewald <robewald@...> wrote:
> $ sbcl
> fatal error encountered in SBCL pid 16343:
> can't find core file at /usr/local/lib/sbcl//sbcl.core
> It works when setting SBCL_HOME=/home/robert/lib/sbcl
> But it bothers me that I cant just run sbcl. What do I do wrong here?
You did nothing wrong -- installing in a non-standard location
requires SBCL_HOME to be set.
1.2. Finding ancillary files
The SBCL runtime needs to be able to find the ancillary files
associated with it: the "sbcl.core" file, and the contrib modules.
Finding core can happen in three ways:
1. By default, in a location configured when the system was built.
For binary distributions this is in "/usr/local/lib/sbcl".
2. By environment variable, in the directory named by the
environment variable "SBCL_HOME". Example:
$ export SBCL_HOME=/foo/bar/lib/sbcl
If your "INSTALL_ROOT" was FOO, then your "SBCL_HOME" is
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 a non-standard location
(e.g. in your user account), instead of installing SBCL on an entire
system. Method #3 is mostly useful for testing or other special
Contributed modules are primarily looked for in "SBCL_HOME", or the
directory the core resides in if "SBCL_HOME" is not set.
ASDF:*CENTRAL-REGISTRY* serves as an additional fallback for