GENERAL INFORMATION

Welcome to SBCL.

To find out more about who created the system, see the "CREDITS" file.

If you'd like information about the legalities of copying the system,
see the "COPYING" file.

If you'd like to install or build the system, see the "INSTALL" file.

If you'd like more information about using the system, see the man
page, "sbcl.1", or the user manual in the "doc/" subdirectory of the
distribution. (The user manual is maintained as DocBook SGML in the
source distribution; there is an HTML version in the binary
distribution.)

The system is a work in progress. See the "TODO" file in the source
distribution for some highlights.

If you'd like to make suggestions, report a bug, or help to improve the
system, please send mail to one of the mailing lists:
  sbcl-help@lists.sourceforge.net
  sbcl-devel@lists.sourceforge.net


SYSTEM-SPECIFIC HINTS

for OpenBSD:
  OpenBSD 3.0 has stricter ulimit values, and/or enforces them more
  strictly, than its predecessors. Therefore SBCL's initial mmap()
  won't work unless you increase the limit on the data segment from
  the OpenBSD defaults, e.g. with
    ulimit -S -d 1000000
  before you run SBCL. Otherwise SBCL fails with a message like
  "ensure_space: failed to validate xxxxxxx bytes at yyyyy". (SBCL
  is just allocating this huge address space, not actually using this
  huge memory at this point. OpenBSD <3.0 had no problem with this,
  but OpenBSD 3.0 is less hospitable.)

for Darwin:
  PURIFY (which can be used alone but is also used by the system when
  saving a new core) uses more stack than the default limit on MacOS
  X.2.  Therefore, in order to get PURIFY to work reliably, you need
  to increase the limit, with e.g.
    limit stack 8192 # for the default shell, tcsh
    ulimit -s 8192 # for bash
  before running SBCL.  This is also necessary when building the system
  from sources, as part of the build process involves saving a new core.