To install Elk on your system do the following:

1) Change into the directory "config" and choose the configuration file
   for your type of system.
   
   The names of the configuration files follow the convention
   "machine-os-compiler", where "machine" identifies the type of
   hardware (CPU, manufacturer, ...), "os" is the operating system
   version, and "compiler" identifies the C compiler to be used to
   compile the sources.

   When you have selected a configuration file, make a symbolic link
   "system" to it (or a hard link, or copy it).

   If you can't find a suitable configuration file for your system,
   create a new one by copying one of the existing files.  Edit the
   new file and change the definitions that need to be changed for
   your type of system.  When you are done and everything works, mail
   the new file to <net@cs.tu-berlin.de>, so that I can make it part of
   the next release of Elk.

   Also, you may find a config file suitable for your platform in
   config/untested.  I haven't tested the current release of Elk with
   any of these config files (either because they are based on
   information provided by users of Elk, or because I have lost
   access to the machines).

2) Edit the file config/site and change the definitions that need to
   be changed for your site.  The directory config/sites holds a few
   locally used site files for different operating systems; you may
   find these useful (in particular the libx* variables).

3) If necessary, edit the top-level Makefile and remove those components
   from SUBDIRS that you don't want to compile and install.

4) Have a look into the file MACHINES for further information and
   potential problems and pitfalls pertaining your type of system.

5) Run "make" and, if it has finished successfully, run "make install".

6) Invoke the interpreter and test it by typing a few Scheme expressions
   and by loading some of the example programs from the "examples"
   directory tree.  Test dynamic loading by evaluating "(load 'unix.o)"
   and then "(system 'date)".

7) [Optional:]  if your system does not support dynamic loading of object
   files, you may want to create an instance of the interpreter that is
   linked together with extensions statically (this requires that
   init_objects has been set to "yes" in config/site).  You can use the
   shell script scripts/linkscheme to do the linking.
