1.0.8.32: improved Git for SBCL Hackers in a few places
[sbcl/lichteblau.git] / make.sh
blob51a36cca0f1b25567ba44ab0640cb6a3cdee13a5
1 #!/bin/sh
2 set -e
4 # "When we build software, it's a good idea to have a reliable method
5 # for getting an executable from it. We want any two reconstructions
6 # starting from the same source to end up in the same result. That's
7 # just a basic intellectual premise."
8 # -- Christian Queinnec, in _Lisp In Small Pieces_, p. 313
10 # This software is part of the SBCL system. See the README file for
11 # more information.
13 # This software is derived from the CMU CL system, which was
14 # written at Carnegie Mellon University and released into the
15 # public domain. The software is in the public domain and is
16 # provided with absolutely no warranty. See the COPYING and CREDITS
17 # files for more information.
19 # The value of SBCL_XC_HOST should be a command to invoke the
20 # cross-compilation Lisp system in such a way that it reads commands
21 # from standard input, and terminates when it reaches end of file on
22 # standard input. Some suitable values are:
23 # "sbcl" to use an existing SBCL binary as a cross-compilation host
24 # "sbcl --sysinit /dev/null --userinit /dev/null"
25 # to use an existing SBCL binary as a cross-compilation host
26 # even though you have stuff in your initialization files
27 # which makes it behave in such a non-standard way that
28 # it keeps the build from working
29 # "sbcl --disable-debugger"
30 # to use an existing SBCL binary as a cross-compilation host
31 # and tell it to handle errors as best it can by itself
32 # (probably by dying with an error code) instead of waiting
33 # endlessly for a programmer to help it out with input
34 # on *DEBUG-IO*
35 # "lisp -batch" to use an existing CMU CL binary as a cross-compilation host
36 # "lisp -noinit -batch"
37 # to use an existing CMU CL binary as a cross-compilation host
38 # when you have weird things in your .cmucl-init file
39 # "openmcl --batch"
40 # to use an OpenMCL binary as a cross-compilation host
41 # "clisp"
42 # to use a CLISP binary as a cross-compilation host
44 # FIXME: Make a more sophisticated command line parser, probably
45 # accepting "sh make.sh --xc-host foolisp" instead of the
46 # the present "sh make.sh foolisp".
47 # FIXME: Tweak this script, and the rest of the system, to support
48 # a second bootstrapping pass in which the cross-compilation host is
49 # known to be SBCL itself, so that the cross-compiler can do some
50 # optimizations (especially specializable arrays) that it doesn't
51 # know how to implement how in a portable way. (Or maybe that wouldn't
52 # require a second pass, just testing at build-the-cross-compiler time
53 # whether the cross-compilation host returns suitable values from
54 # UPGRADED-ARRAY-ELEMENT-TYPE?)
56 LANG=C
57 LC_ALL=C
58 export LANG LC_ALL
60 build_started=`date`
61 echo "//starting build: $build_started"
63 if [ "$OSTYPE" = "cygwin" -o "$OSTYPE" = "msys" ] ; then
64 DEVNULL=NUL
65 else
66 DEVNULL=/dev/null
68 SBCL_XC_HOST="${1:-sbcl --disable-debugger --userinit $DEVNULL --sysinit $DEVNULL}"
69 export DEVNULL
70 export SBCL_XC_HOST
71 echo //SBCL_XC_HOST=\"$SBCL_XC_HOST\"
73 . ./find-gnumake.sh
74 find_gnumake
76 # If you're cross-compiling, you should probably just walk through the
77 # make-config.sh script by hand doing the right thing on both the host
78 # and target machines.
79 sh make-config.sh
81 # Enforce the source policy for no bogus whitespace
82 tools-for-build/canonicalize-whitespace
84 # The make-host-*.sh scripts are run on the cross-compilation host,
85 # and the make-target-*.sh scripts are run on the target machine. In
86 # ordinary compilation, we just do these phases consecutively on the
87 # same machine, but if you wanted to cross-compile from one machine
88 # which supports Common Lisp to another which does not (yet:-) support
89 # Common Lisp, you could do something like this:
90 # Create copies of the source tree on both the host and the target.
91 # Read the make-config.sh script carefully and emulate it by hand
92 # on both machines (e.g. creating "target"-named symlinks to
93 # identify the target architecture).
94 # On the host system:
95 # SBCL_XC_HOST=<whatever> sh make-host-1.sh
96 # Copy src/runtime/genesis/*.h from the host system to the target
97 # system.
98 # On the target system:
99 # sh make-target-1.sh
100 # Copy src/runtime/sbcl.nm and output/stuff-groveled-from-headers.lisp
101 # from the target system to the host system.
102 # On the host system:
103 # SBCL_XC_HOST=<whatever> sh make-host-2.sh
104 # Copy output/cold-sbcl.core from the host system to the target system.
105 # On the target system:
106 # sh make-target-2.sh
107 # sh make-target-contrib.sh
108 # Or, if you can set up the files somewhere shared (with NFS, AFS, or
109 # whatever) between the host machine and the target machine, the basic
110 # procedure above should still work, but you can skip the "copy" steps.
111 time sh make-host-1.sh
112 time sh make-target-1.sh
113 time sh make-host-2.sh
114 time sh make-target-2.sh
115 time sh make-target-contrib.sh
117 NCONTRIBS=`find contrib -name Makefile -print | wc -l`
118 NPASSED=`find contrib -name test-passed -print | wc -l`
119 echo
120 echo "The build seems to have finished successfully, including $NPASSED (out of $NCONTRIBS)"
121 echo "contributed modules. If you would like to run more extensive tests on"
122 echo "the new SBCL, you can try:"
123 echo
124 echo " cd tests && sh ./run-tests.sh"
125 echo
126 echo " (All tests should pass on x86/Linux, x86/FreeBSD4, and ppc/Darwin. On"
127 echo " other platforms some failures are currently expected; patches welcome"
128 echo " as always.)"
129 echo
130 echo "To build documentation:"
131 echo
132 echo " cd doc/manual && make"
133 echo
134 echo "To install SBCL (more information in INSTALL):"
135 echo
136 echo " sh install.sh"
138 build_finished=`date`
139 echo
140 echo "//build started: $build_started"
141 echo "//build finished: $build_finished"