#!/bin/sh
+set -e
+
+LANG=C
+LC_ALL=C
+export LANG LC_ALL
# "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.
# provided with absolutely no warranty. See the COPYING and CREDITS
# files 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:
-# "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
-# "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
-# when you have weird things in your .cmucl-init file
-#
-# FIXME: Make a more sophisticated command line parser, probably
-# accepting "sh make.sh --xc-host foolisp" instead of the
-# the present "sh make.sh foolisp".
-# FIXME: Tweak this script, and the rest of the system, to support
-# a second bootstrapping pass in which the cross-compilation host is
-# known to be SBCL itself, so that the cross-compiler can do some
-# optimizations (especially specializable arrays) that it doesn't
-# know how to implement how in a portable way. (Or maybe that wouldn't
-# 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}"
-echo //SBCL_XC_HOST=\"$SBCL_XC_HOST\"
+# If you're cross-compiling, make-config.sh should "do the right
+# thing" when run on the target machine, with the minor caveat that
+# any --xc-host parameter should be suitable for the host machine
+# instead of the target.
+sh make-config.sh "$@" || exit $?
+
+. output/prefix.def
+. output/build-config
+
+build_started=`date`
+echo "//Starting build: $build_started"
+# Apparently option parsing succeeded. Print out the results.
+echo "//Options: --prefix='$SBCL_PREFIX' --xc-host='$SBCL_XC_HOST'"
-# If you're cross-compiling, you should probably just walk through the
-# make-config.sh script by hand doing the right thing on both the host
-# and target machines.
-sh make-config.sh || exit 1
+# Enforce the source policy for no bogus whitespace
+tools-for-build/canonicalize-whitespace
# 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
# 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.
+# Copy src/runtime/genesis/*.h from the host system to the target
+# system.
# On the target system:
# sh make-target-1.sh
-# Copy src/runtime/sbcl.nm from the target system to the host system.
+# Copy src/runtime/sbcl.nm and output/stuff-groveled-from-headers.lisp
+# from the target system to the host system.
# On the host system:
# SBCL_XC_HOST=<whatever> sh make-host-2.sh
# Copy output/cold-sbcl.core from the host system to the target system.
# On the target system:
-# sh make-host-2.sh
-sh make-host-1.sh || exit 1
-sh make-target-1.sh || exit 1
-sh make-host-2.sh || exit 1
-sh make-target-2.sh || exit 1
+# sh make-target-2.sh
+# sh make-target-contrib.sh
+# Or, if you can set up the files somewhere shared (with NFS, AFS, or
+# whatever) between the host machine and the target machine, the basic
+# procedure above should still work, but you can skip the "copy" steps.
+time sh make-host-1.sh
+time sh make-target-1.sh
+time sh make-host-2.sh
+time sh make-target-2.sh
+time sh make-target-contrib.sh
+
+NCONTRIBS=`find contrib -name Makefile -print | wc -l`
+NPASSED=`find obj/asdf-cache -name test-passed.test-report -print | wc -l`
+echo
+echo "The build seems to have finished successfully, including $NPASSED (out of $NCONTRIBS)"
+echo "contributed modules. If you would like to run more extensive tests on"
+echo "the new SBCL, you can try:"
+echo
+echo " cd tests && sh ./run-tests.sh"
+echo
+echo " (All tests should pass on x86/Linux, x86/FreeBSD4, and ppc/Darwin. On"
+echo " other platforms some failures are currently expected; patches welcome"
+echo " as always.)"
+echo
+echo "To build documentation:"
+echo
+echo " cd doc/manual && make"
+echo
+echo "To install SBCL (more information in INSTALL):"
+echo
+echo " sh install.sh"
+
+# This is probably the best place to ensure people will see this.
+if test -n "$legacy_xc_spec"
+then
+ echo <<EOF
+******************************************************************************
+**
+** Old-style XC-host specification detected: '$SBCL_XC_HOST'
+**
+** Since 1.0.41.45 SBCL expects the XC-host to be specified using
+** the --xc-host='myhost' command line option, not with a positional
+** argument. The legacy style still works, but will not be supported
+** indefinitely. Please update your build procedure.
+**
+******************************************************************************
+EOF
+fi
+
+build_finished=`date`
+echo
+echo "//build started: $build_started"
+echo "//build finished: $build_finished"
projects / sbcl.git / blobdiff