The SBCL runtime needs to be able to find the ancillary files
associated with it: the "sbcl.core" file, and the contrib modules.
The SBCL runtime needs to be able to find the ancillary files
associated with it: the "sbcl.core" file, and the contrib modules.
1. By default, in a location configured when the system was built.
For binary distributions this is in "/usr/local/lib/sbcl".
1. By default, in a location configured when the system was built.
For binary distributions this is in "/usr/local/lib/sbcl".
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
cases.
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
cases.
* Check that the host lisp you're building with is known to work
as an SBCL build host, and the your OS is supported.
* Check that the host lisp you're building with is known to work
as an SBCL build host, and the your OS is supported.
* Some GCC versions are known to have bugs that affect SBCL
compilation: if the error you're encountering seems related to
* Some GCC versions are known to have bugs that affect SBCL
compilation: if the error you're encountering seems related to
Note that every release isn't tested with every possible host
compiler. You're most likely to get a clean build with SBCL itself
Note that every release isn't tested with every possible host
compiler. You're most likely to get a clean build with SBCL itself