DataMuseum.dk

top - download

    Length: 2679 (0xa77)
    Types: TextFile
    Names: »INSTALL«

└─⟦a0efdde77⟧ Bits:30001252 EUUGD11 Tape, 1987 Spring Conference Helsinki
    └─ ⟦this⟧ »EUUGD11/gnu-31mar87/scheme/INSTALL« 

TextFile

READ THIS FILE FIRST, then

 o Read Install.unx for more information on how to install CScheme
   under Unix.

 o Read Install.vms for more information on how to install CScheme
   under VMS.

Known problems:
- Do not try to bring up CScheme on machines on which C longs
are less than 32 bits unless you are willing to put weeks of work into
it.  We're not even sure it is feasible without major redesign.

- If your machine does not use the ASCII character encoding,
you may be in for serious trouble.  The code in a few places does
explicit ASCII case conversions, and although we plan to remove all
such dependencies, we have not yet done it.  In particular, the file
string.c is known to have this problem.

- The bignum (infinite(?) precision integers) code may have problems
due to unsigned declarations being dropped by compilers (in addition
to any coding and algorithmic bugs, which bignum code is notorious
for).  If you have problems with unsignedness/overflow, you may want
to try forcing it to use characters as digits rather than shorts.
Look at bignum.h.

If your machine is not one of the supported ones, you manage to get
CScheme up on it, and would like to have an easier time with the next
release, please let us know, and send us the modified files so that we
can incorporate your changes into the released sources.

IF YOU ARE RUNNING NEITHER UNIX NOR VMS ...

... you will have to do some extra work.  The files Install.unx and
Install.vms may be of some help, but you'll have to filter out the
information which you can use.

Look for the file config.dst.  (If the scheme directory has
subdirectories corresponding to the unix hierarchy, it should be in
the microcode subdirectory).  Edit it as appropriate for your machine
and save it as config.h (the file Install.unx gives an overview, and
config.dst contains a detailed explanation of each definition).

Follow the installation procedure explained in Install.vms, after
modifying all the ".com" files to fit your command interpreter and
system.  "@ing" a file on VMS means to give it as input to the
command interpreter ("SOURCEing" a file on the Unix C-shell, or
"TAKEing" a file on TOPS-20).

Note that scheme will use the unknown.c operating system file.  Among
other things, this means that there will be no interrupt characters,
no immediate IO, and a fair amount of operating system dependent
procedures (time, date, file manipulation, etc.) will be missing.  
If they can be implemented on your system and you feel up to the task,
you can use unix.c and vms.c for guidance.

If you run into problems not described above, get in touch with us
(see README) and we may be able to help.  Good luck!