Installation of the provided binaries

To install this software, copy scrt/objects.h to include:sc/objects.h.
Then copy sci and scc from either 000/sc? (68000 binaries) or 020/sc?
(68020/68881 binaries) to wherever in your path you would like them to
live. You may then use scc and sci; see the various files in "docs" for
more information.

	Changes for the Amiga

The "save-heap" and "restore-heap" facilities are probably not
possible on the Amiga; I decided not to worry about them. As a result,
the compiler re-initializes itself every time it is run. There is no
rusage information available. Other than that, the scheme environment
has not been changed. The "front end" portion of the compiler was
modified to work with SAS C instead of a Unix C, and the "profiled"
compile switch was disabled. Those are the only changes to the scheme
sources in either the interpreter or the compiler that are anything
but minor tweaks for SAS C.

	System requirements

5.10a can be used as a target for the compiler. However, you will need
SAS C 5.10b to build the system from scratch, as bugs in 5.10a cause
the garbage collection code to fail. See "Building with 5.10a or a 3
meg heap" for information on how to build it with 5.10a.  I suspect
that any 5.10 can be used as a target for the compiler, but have only
tested 5.10a and b.

The interpreter (sci) should run on a 1.5 Meg system, and the compiler
(scc) on a 2 Meg system. However, I recommend at least a 2 meg heap
for anything but trivial compiles, and 3 for anything serious.  All
scheme files except scsc/transform.sc can be compiled with a 3 meg
heap; transform.sc requires a 4 meg heap. This means you need (at
least) a 5 meg amiga to rebuild the system from scratch. However, I've
provided enough that it may not be required; see "Building with 5.10a
or a 3 meg heap".

	Building the system from scratch

Build is a rexx script in the top-level directory. It will read the
file name given as an argument, and process it in a manner similar to
make, except on a line-by-line basis instead of the entire file. As a
result, the scripts can be used as execute scripts directly. For more
information on build, see the file "build.rexx".

To build from C source, use the build script "fromc". To build from
scheme sources, use the build script "fromsc". If you have Rexx, the
scripts will work directly. If you don't have rexx, the "build" in the
last line of the fromsc script will need to be changed to an "execute".

To build the system, first cd to scrt, run sascoption to set the
processor types correctly (the default is 68030/68881). If you are
running 1.3, edit the select function at the end of cio.c. The second
parameter WaitForChar should be 1, not 0, to avoid a bug in the pre
2.0 timer.device. Now execute "fromc" and get a cup of coffee. After
the build, the file sc.lib should be copid to lib:, objects.h to
include:sc, and sci to wherever on your path you wish it to live. Next
cd to scsc, run sascoptions, and execute fromc again. Then copy Xscc
to wherever you wish it to live as "scc." At this point, you can
rebuild the system from scheme by execute "fromsc" in each directory
instead of fromsc.

	Building with 5.10a or a 3 meg heap.

I've provided a copy of scrt/heap.o the one file that stumbles over
the bugs in 5.10a.  By preserving this file, you can rebuild the
system with 5.10a and the provided binaries. Make sure you do not
overwrite scrt/heap.o until you have 5.10b. 

Likewise, I have provided a copy of scsc/transform.c. This is the only
scheme file that cannot be compiled to C with a 3 meg heap. You can
rebuild the system from scheme with this file and the provided
binaries.