X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=INSTALL;h=684aaf218362c81fc06a8e3ba296a18a798e8304;hb=7c7e6276719b8d40fddec2070cad81064a25c8ed;hp=b6acdbc1cceae3ad3568fbb79c041b469442abc2;hpb=c05927ab82e234da99f8409038e7e338e36ddf8e;p=sbcl.git diff --git a/INSTALL b/INSTALL index b6acdbc..684aaf2 100644 --- a/INSTALL +++ b/INSTALL @@ -39,7 +39,7 @@ INSTALLING SBCL The SBCL runtime needs to be able to find the ancillary files associated with it: the "sbcl.core" file, and the contrib modules. - This can happen in three ways: + 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". @@ -57,15 +57,17 @@ INSTALLING SBCL $ sbcl --core /foo/bar/sbcl.core - When using this option contrib modules are looked for in the - directory where the designated core resides, and in "SBCL_HOME". - 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. + 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 + ASDF-based modules. + 1.3. Anatomy of SBCL The two files that SBCL needs to run, at minimum, are: @@ -143,9 +145,9 @@ INSTALLING SBCL or extra debugging code. The preferred way to do this is by creating a file - "customize-target-features.lisp-expr", containing a lambda - expression which is applied to the default *FEATURES* set and which - returns the new *FEATURES* set, e.g. + "customize-target-features.lisp", containing a lambda expression + which is applied to the default *FEATURES* set and which returns the + new *FEATURES* set, e.g. (lambda (features) (flet ((enable (x) @@ -185,6 +187,10 @@ INSTALLING SBCL * Check that the host lisp you're building with is known to work as an SBCL build host, and the your OS is supported. + + * Try to do a build without loading any initialization files + for the cross-compilation host (for example + "sh make.sh 'sbcl --userinit /dev/null --sysinit /dev/null'"). * Some GCC versions are known to have bugs that affect SBCL compilation: if the error you're encountering seems related to @@ -232,7 +238,7 @@ INSTALLING SBCL x86 PPC Alpha Sparc HPPA MIPS MIPSel Linux 2.2, 2.4, 2.6 X X X X X X X FreeBSD X - OpenBSD 3.4, 3.5 X + OpenBSD 3.4, 3.5 X NetBSD X Solaris X Tru64 X