0.7.4.21:

[sbcl.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 728f6db..f987259 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -48,11 +48,22 @@ This software has been built successfully on these systems:
                os = FreeBSD 3.4 or 4.0
                        host lisp = CMU CL
                        host lisp = SBCL itself
-               os = OpenBSD 2.6
+               os = OpenBSD 2.6, 2.7, 2.8, 2.9, and 3.0
                        host lisp = SBCL itself
-It is known not to build under CLISP, because CLISP doesn't support
-MAKE-LOAD-FORM. Reports of other systems that it works on, or help in
-making it run on more systems, would be appreciated.
+       cpu = sparc
+               os = Debian GNU/Linux 2.2 with libc >= 2.2
+                       host lisp = SBCL itself
+               os = Solaris 8
+                       host lisp = SBCL itself
+It is known not to build under CLISP because of (as of early June 2002)
+bugs in the CLISP garbage collector, and it is known not to build under
+other systems like OpenMCL because of (as of early June 2002) remaining
+dependencies of SBCL bootstrapping on CMUCLisms like the representation
+of BYTE. 
+
+Reports of other systems that it works on (or doesn't work on, for
+that matter), or help in making it run on more systems, would be
+appreciated.
 
                CAUTION CAUTION CAUTION CAUTION CAUTION
            SBCL, like CMU CL, overcommits memory. That is, it
@@ -94,16 +105,21 @@ To build the system binaries:
      per the CAUTION note above. (As of version 0.6.0, the most
      memory-intensive operation in make.sh is the second call to
      GENESIS, which makes the Lisp image grow to nearly 128 Mb RAM+swap.
-     This will probably be reduced somewhat in some later version
-     by allowing cold load of byte-compiled files, so that the cold
-     image can be smaller.)
   2. If the GNU make command is not available under the name "gmake",
      then define the environment variable GNUMAKE to a name where it can
      be found.
-  3. If you like, you can edit the base-target-features.lisp-expr file
-     to customize the resulting Lisp system. By enabling or disabling
-     features in this file, you can create a smaller system, or one
-     with extra code for debugging output or error-checking or other things.
+  3. If you like, you can tweak the *FEATURES* set for the resulting
+     Lisp system, enabling or disabling features like documentation
+     strings or extra debugging code. The preferred way to do this is
+     by creating a file "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 (LIST)
+         (ADJOIN :SB-SHOW
+                 (REMOVE :SB-DOC
+                         LIST)))
+     (This is the preferred way because it lets local changes interact
+     cleanly with CVS changes to the main, global source tree.)
   4. Run "sh make.sh" in the same directory where you unpacked the 
      tarball. If you don't already have a SBCL binary installed
      as "sbcl" in your path, you'll need to tell make.sh what Lisp