mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
7d407220e1
* Over time, the process for producing an SBCL build for another target architecture or OS has become more difficult and less documented. * Move all make.sh argument processing to make-config.sh. * Have make-config.sh produce a file, output/build-config, containing shell commands to set up important build parameters such as where to find GNUMAKE, what SBCL_XC_HOST is, and so on. * Source output/build-config in most of the make*.sh scripts. * The practical upshot of all this is that a cross-compile build is now a matter of alternating between target and host, calling make-config.sh, make-host-1.sh, make-target-1.sh, make-host-2.sh, make-target-2.sh, and following up with a make-target-contrib.sh on the target, and you wind up with a usable product. And, as make-config.sh does all of the arg parsing, you can pass --xc-host= or --dynamic-space-size= or whatever and it all works out. |
||
|---|---|---|
| contrib | ||
| doc | ||
| git | ||
| src | ||
| tests | ||
| tools-for-build | ||
| .cvsignore | ||
| .gitignore | ||
| base-target-features.lisp-expr | ||
| binary-distribution.sh | ||
| BUGS | ||
| build-order.lisp-expr | ||
| clean.sh | ||
| common-lisp-exports.lisp-expr | ||
| COPYING | ||
| CREDITS | ||
| distclean.sh | ||
| find-gnumake.sh | ||
| generate-version.sh | ||
| HACKING | ||
| html-distribution.sh | ||
| INSTALL | ||
| install.sh | ||
| make-config.sh | ||
| make-genesis-2.lisp | ||
| make-genesis-2.sh | ||
| make-host-1.lisp | ||
| make-host-1.sh | ||
| make-host-2.lisp | ||
| make-host-2.sh | ||
| make-target-1.sh | ||
| make-target-2-load.lisp | ||
| make-target-2.lisp | ||
| make-target-2.sh | ||
| make-target-contrib.sh | ||
| make-windows-installer.sh | ||
| make.sh | ||
| NEWS | ||
| OPTIMIZATIONS | ||
| package-data-list.lisp-expr | ||
| PRINCIPLES | ||
| pubring.pgp | ||
| README | ||
| release.sh | ||
| run-sbcl.sh | ||
| sbcl-pwd.sh | ||
| slam.sh | ||
| source-distribution.sh | ||
| tagify.sh | ||
| TLA | ||
| TODO | ||
| wc.sh | ||
GENERAL INFORMATION
Welcome to SBCL.
If you'd like to install or build the system, see the "INSTALL" file.
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 more information about using the system, see the man
page, "sbcl.1", or the user manual in the "doc/manual" subdirectory of
the distribution. (The user manual is maintained as Texinfo in the
source distribution; HTML version is available for download, and
"INSTALL" describes how to build the Texinfo version in HTML and PDF.)
The system is a work in progress. See the "TODO" file in the source
distribution for some highlights.
The "BUGS" file lists current known bugs.
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
Note that as a spam reduction measure you must subscribe to the lists
before you can post.
SYSTEM-SPECIFIC HINTS
for NetBSD:
NetBSD 2.0 and above are required because of the lack of needed
signal APIs in NetBSD 1.6 and earlier.
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.)