5 To find out more about who created the system, see the "CREDITS" file.
7 If you'd like information about the legalities of copying the system,
8 see the "COPYING" file.
10 If you'd like to install or build the system, see the "INSTALL" file.
12 If you'd like more information about using the system, see the man
13 page, "sbcl.1", or the user manual in the "doc/" subdirectory of the
14 distribution. (The user manual is maintained as DocBook SGML in the
15 source distribution; there is an HTML version in the binary
18 The system is a work in progress. See the "TODO" file in the source
19 distribution for some highlights.
21 If you'd like to make suggestions, report a bug, or help to improve the
22 system, please send mail to one of the mailing lists:
23 sbcl-help@lists.sourceforge.net
24 sbcl-devel@lists.sourceforge.net
25 Note that as a spam reduction measure you must subscribe to the lists
32 NetBSD 2.0 and above are required because of the lack of needed
33 signal APIs in NetBSD 1.6 and earlier.
36 OpenBSD 3.0 has stricter ulimit values, and/or enforces them more
37 strictly, than its predecessors. Therefore SBCL's initial mmap()
38 won't work unless you increase the limit on the data segment from
39 the OpenBSD defaults, e.g. with
41 before you run SBCL. Otherwise SBCL fails with a message like
42 "ensure_space: failed to validate xxxxxxx bytes at yyyyy". (SBCL
43 is just allocating this huge address space, not actually using this
44 huge memory at this point. OpenBSD <3.0 had no problem with this,
45 but OpenBSD 3.0 is less hospitable.)
48 PURIFY (which can be used alone but is also used by the system when
49 saving a new core) uses more stack than the default limit on MacOS
50 X.2. Therefore, in order to get PURIFY to work reliably, you need
51 to increase the limit, with e.g.
52 limit stack 8192 # for the default shell, tcsh
53 ulimit -s 8192 # for bash
54 before running SBCL. This is also necessary when building the system
55 from sources, as part of the build process involves saving a new core.