X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=make.sh;h=b3b47fa6f4ba385c3dc4484cd94bceefb01dc603;hb=df679ed627975948b1cee190f4d79c397588c43e;hp=e8d0044170ab243903965d2feeb1820a79057afb;hpb=a530bbe337109d898d5b4a001fc8f1afa3b5dc39;p=sbcl.git diff --git a/make.sh b/make.sh index e8d0044..b3b47fa 100755 --- a/make.sh +++ b/make.sh @@ -4,7 +4,7 @@ # 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. @@ -18,17 +18,27 @@ # 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 --disable-debugger" +# to use an existing SBCL binary as a cross-compilation host +# and tell it to handle errors as best it can by itself +# (probably by dying with an error code) instead of waiting +# endlessly for a programmer to help it out with input +# on *DEBUG-IO* # "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 +# "openmcl --batch" +# to use an OpenMCL binary as a cross-compilation host +# "clisp" +# to use a CLISP binary as a cross-compilation host # # FIXME: Make a more sophisticated command line parser, probably # accepting "sh make.sh --xc-host foolisp" instead of the @@ -41,37 +51,75 @@ # 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}" +# FIXME: --noprogrammer was deprecated in sbcl-0.7.5, replaced by +# --disable-debugger. We still use the old form here because the +# change was not preannounced, and it would be rude to make our new +# version of SBCL unbootstrappable by immediately prior versions. +# But in a year or so the --noprogrammer here can change to +# --disable-debugger (and the deprecated --noprogrammer support can +# go away completely). +SBCL_XC_HOST="${1:-sbcl --noprogrammer}" +export SBCL_XC_HOST echo //SBCL_XC_HOST=\"$SBCL_XC_HOST\" +# the GNU dialect of "make" -- easier to find or port it than to +# try to figure out how to port to the local dialect... +if [ "$GNUMAKE" != "" ] ; then + # The user is evidently trying to tell us something. + GNUMAKE="$GNUMAKE" +elif [ -x "`which gmake`" ] ; then + # "gmake" is the preferred name in *BSD. + GNUMAKE=gmake +else + # FIXME: Now that we do this early, maybe prompt the user rather + # than guessing? I'd still be annoyed, though... -- CSR, + # 2003-05-16. + # + # All the world's a Linux, and all its users weary of cautious + # BSDish worries that "make" might not be GNU make; so just guess + # that "make" is GNU make and hope for the best. + GNUMAKE=make +fi + +export GNUMAKE +echo //GNUMAKE=\"$GNUMAKE\" + + # 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 -# 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= 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= 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-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. 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 +date