+
#!/bin/sh
# "When we build software, it's a good idea to have a reliable method
# for getting an executable from it. We want any two reconstructions
# starting from the same source to end up in the same result. That's
# just a basic intellectual premise."
-# -- Christian Quinnec, in _Lisp In Small Pieces_, p. 313
+# -- Christian Queinnec, in _Lisp In Small Pieces_, p. 313
# This software is part of the SBCL system. See the README file for
# more information.
# The value of SBCL_XC_HOST should be a command to invoke the
# cross-compilation Lisp system in such a way that it reads commands
# from standard input, and terminates when it reaches end of file on
-# standard input. Suitable values are:
+# standard input. Some suitable values are:
# "sbcl" to use an existing SBCL binary as a cross-compilation host
# "sbcl --sysinit /dev/null --userinit /dev/null"
# to use an existing SBCL binary as a cross-compilation host
# even though you have stuff in your initialization files
# which makes it behave in such a non-standard way that
# it keeps the build from working
+# "sbcl --noprogrammer"
+# to use an existing SBCL binary as a cross-compilation host
+# and tell it to handle errors as best it can by itself,
+# without trying to use *DEBUG-IO* to ask for help from
+# the programmer
# "lisp -batch" to use an existing CMU CL binary as a cross-compilation host
# "lisp -noinit -batch"
# to use an existing CMU CL binary as a cross-compilation host
# require a second pass, just testing at build-the-cross-compiler time
# whether the cross-compilation host returns suitable values from
# UPGRADED-ARRAY-ELEMENT-TYPE?)
-export SBCL_XC_HOST="${1:-sbcl}"
+export SBCL_XC_HOST="${1:-sbcl --noprogrammer}"
echo //SBCL_XC_HOST=\"$SBCL_XC_HOST\"
# If you're cross-compiling, you should probably just walk through the
# and target machines.
sh make-config.sh || exit 1
-# The foo-host-bar.sh scripts are run on the cross-compilation host,
-# and the foo-target-bar.sh scripts are run on the target machine. In
+# The make-host-*.sh scripts are run on the cross-compilation host,
+# and the make-target-*.sh scripts are run on the target machine. In
# ordinary compilation, we just do these phases consecutively on the
# same machine, but if you wanted to cross-compile from one machine
-# which supports Common Lisp to another which does not (yet) support
-# Lisp, you could do something like this:
-# Create copies of the source tree on both host and target.
-# Create links from "target" to "x86" in "src/compiler/" and
-# in "src/assembly/", on both the host and the target. (That
-# would ordinarily be done by the make.sh code above; if we're
-# doing make.sh stuff by hand, we need to do this by hand, too.)
+# which supports Common Lisp to another which does not (yet:-) support
+# Common Lisp, you could do something like this:
+# Create copies of the source tree on both the host and the target.
+# Read the make-config.sh script carefully and emulate it by hand
+# on both machines (e.g. creating "target"-named symlinks to
+# identify the target architecture).
# On the host system:
# SBCL_XC_HOST=<whatever> sh make-host-1.sh
# Copy src/runtime/sbcl.h from the host system to the target system.
sh make-target-1.sh || exit 1
sh make-host-2.sh || exit 1
sh make-target-2.sh || exit 1
+date
projects / sbcl.git / blobdiff