projects
/
sbcl.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
1.0.29.1: fix FILL
[sbcl.git]
/
INSTALL
diff --git
a/INSTALL
b/INSTALL
index
ed2e32a
..
018ef58
100644
(file)
--- a/
INSTALL
+++ b/
INSTALL
@@
-19,9
+19,14
@@
INSTALLING SBCL
1.1. Quick start:
1.1. Quick start:
+ To run SBCL without installing it, from the top of binary distribution
+ directory:
+
+ $ sh run-sbcl.sh
+
The following command installs SBCL and related documentation under
the "/usr/local" directory:
The following command installs SBCL and related documentation under
the "/usr/local" directory:
-
+
# INSTALL_ROOT=/usr/local sh install.sh
You can also install SBCL as a user, under your home directory:
# INSTALL_ROOT=/usr/local sh install.sh
You can also install SBCL as a user, under your home directory:
@@
-31,7
+36,7
@@
INSTALLING SBCL
In other words, "install.sh" installs SBCL under the directory named
by the environment variable "INSTALL_ROOT".
In other words, "install.sh" installs SBCL under the directory named
by the environment variable "INSTALL_ROOT".
- If you install SBCL from binary distribution in other location then
+ If you install SBCL from binary distribution in other location than
"/usr/local", see section 1.2, "Finding ancillary files".
1.2. Finding ancillary files
"/usr/local", see section 1.2, "Finding ancillary files".
1.2. Finding ancillary files
@@
-115,7
+120,7
@@
INSTALLING SBCL
been installed under its default name "lisp") as the
cross-compilation host:
been installed under its default name "lisp") as the
cross-compilation host:
- $ sh make.sh 'lisp -batch'
+ $ sh make.sh 'lisp -batch -noinit'
The build may take a long time, especially on older hardware. A
successful build ends with a message beginning: "The build seems to
The build may take a long time, especially on older hardware. A
successful build ends with a message beginning: "The build seems to
@@
-154,10
+159,9
@@
INSTALLING SBCL
(pushnew x features))
(disable (x)
(setf features (remove x features))))
(pushnew x features))
(disable (x)
(setf features (remove x features))))
- ;; Threading support, available on x86 Linux only.
- (enable :sb-thread)
- ;; Slightly smaller core
- (disable :sb-doc)))
+ ;; Threading support, available only on x86/x86-64 Linux, x86 Solaris
+ ;; and x86 Mac OS X (experimental).
+ (enable :sb-thread)))
This is the preferred way because it lets local changes interact
cleanly with CVS changes to the main, global source tree.
This is the preferred way because it lets local changes interact
cleanly with CVS changes to the main, global source tree.
@@
-176,7
+180,7
@@
INSTALLING SBCL
Segfaults on Fedora
Try disabling exec-shield. The easiest way is to use
Segfaults on Fedora
Try disabling exec-shield. The easiest way is to use
- setarch: "setarch i386 sbcl".
+ setarch: "setarch i386 -R sbcl".
Build crashes mysteriously, machine becomes unstable, etc
Build crashes mysteriously, machine becomes unstable, etc
@@
-187,7
+191,7
@@
INSTALLING SBCL
* Check that the host lisp you're building with is known to work as
an SBCL build host, and that your operating system is supported.
* Check that the host lisp you're building with is known to work as
an SBCL build host, and that your operating system 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'").
* 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'").
@@
-209,9
+213,9
@@
INSTALLING SBCL
itself, it's a good idea.) Follow the "CVS Repository" link on
<http://sourceforge.net/projects/sbcl> for instructions.
itself, it's a good idea.) Follow the "CVS Repository" link on
<http://sourceforge.net/projects/sbcl> for instructions.
-2.5. Supported platforms
+2.5. Supported platforms
- Last updated for SBCL 0.8.10.61 (2004-05-28).
+ Last updated for SBCL 0.9.3.74 (2005-08-20).
All of the following platforms are supported in the sense of "should
work", but some things like loading foreign object files may lag
All of the following platforms are supported in the sense of "should
work", but some things like loading foreign object files may lag
@@
-226,32
+230,38
@@
INSTALLING SBCL
SBCL
CMUCL
SBCL
CMUCL
- OpenMCL
- CLISP (recent versions only)
+ CCL (formerly known as OpenMCL)
ABCL (recent versions only)
ABCL (recent versions only)
+ CLISP (only some versions: 2.44.1 is OK, 2.47 is not)
+ XCL
+
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
- as host, otherwise OpenMCL on a PPC and CMUCL elsewhere.
+ as host, otherwise CCL on a PPC and CMUCL elsewhere.
Supported operating systems and architectures:
Supported operating systems and architectures:
- x86 PPC Alpha Sparc HPPA MIPS MIPSel
- Linux 2.2, 2.4, 2.6 X X X X X X X
- FreeBSD X
+ x86 x86-64 PPC Sparc Alpha MIPS MIPSel
+ Linux 2.2, 2.4, 2.6 X X X X X X X
+ Darwin (Mac OS X) X X X
+ Solaris X X
+ FreeBSD X X
+ NetBSD X X
OpenBSD 3.4, 3.5 X
OpenBSD 3.4, 3.5 X
- NetBSD X
- Solaris X
- Tru64 X
- Darwin (Mac OS X) X
+ Windows X
- Some operating systems are more equal then others: most of the
- development and testing is done on x86 Linux and *BSD, PPC Linux
- and Mac OS X.
+ Some operating systems are more equal than others: most of the
+ development and testing is done on x86/x86-64 Linux and x86/PPC
+ Mac OS X.
If an underprivileged platform is important to you, you can help
If an underprivileged platform is important to you, you can help
- by eg. testing during the monthly freeze periods, and most
+ by e.g. testing during the monthly freeze periods, and most
importantly by reporting any problems.
importantly by reporting any problems.
- If you need support beyond what is available on the mailing lists,
- see "Consultants" in the "SUPPORT" file.
+ For further support, see Getting Support and Reporting Bugs
+ in the manual, or
+
+ http://www.sbcl.org/manual/Getting-Support-and-Reporting-Bugs.html
+
+ if you do not have the manual for some reason.