# But in a year or so the --noprogrammer here can change to
# --disable-debugger (and the deprecated --noprogrammer support can
# go away completely).
+
+build_started=`date`
+echo "//starting build: $build_started"
+
SBCL_XC_HOST="${1:-sbcl --noprogrammer}"
export SBCL_XC_HOST
echo //SBCL_XC_HOST=\"$SBCL_XC_HOST\"
# 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.
-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-contrib.sh || exit 1
+time sh make-host-1.sh || exit 1
+time sh make-target-1.sh || exit 1
+time sh make-host-2.sh || exit 1
+time sh make-target-2.sh || exit 1
+time sh make-target-contrib.sh || exit 1
# Sometimes people used to see the "No tests failed." output from the last
# DEFTEST in contrib self-tests and think that's all that is. So...
NPASSED=`find contrib -name test-passed -print | wc -l`
echo
-echo The build seems to have finished successfully, including $NPASSED
-echo (out of $NCONTRIBS) contributed modules. If you would like to run
-echo more extensive tests on the new SBCL, you can try
+echo "The build seems to have finished successfully, including $NPASSED"
+echo "(out of $NCONTRIBS) contributed modules. If you would like to run"
+echo "more extensive tests on the new SBCL, you can try"
echo " cd tests && sh ./run-tests.sh"
echo "(but expect some failures on non-x86 platforms)."
-date
+build_finished=`date`
+echo
+echo "//build started: $build_started"
+echo "//build finished: $build_finished"