WCL only runs on SPARCStations under SunOS 4.1 right now. 
See wcl.text for porting information.

INSTALLATION
------------

If you just want to install WCL without thinking about anything else,
cd to the main wcl directory and type "make install".  This
will cause Lisp to compile and link itself from the sources.  You
might want to read about configuration before doing this, however.
Installing WCL takes roughly 4.5 hours on a SparcStation 1+ and
will require a peak of 50 megabytes of disk space.

When the installation is complete, the newly built binaries will be in
the bin directory, and the newly built libraries will be in the lib
directory. The binaries and libraries that came with the distribution
will be in the dist-bin and dist-lib directories. You can delete the 
dist-* directories you want.

If you want to conserve disk space after WCL has been installed, you may
delete everything but the lib, bin and include directories.

If you want to debug Lisp code, you should also install WGDB,
a modified version of GDB, which is distributed separately.

Refer to doc/wcl.text for information about running and debugging WCL.

CONFIGURATION
---------------------

The CONFIGURATION file in the top-level of the distribution tree
controls how WCL will be rebuilt from sources when doing an
installation. The value of the CC parameter controls which C compiler
will be used by WCL.  Either Sun cc or GCC 2.1. can be used, but GCC
2.1 is preferred because it can generate optimized,
postition-independent code WITH debugging information.
GCC 2.2.2 DOES NOT WORK WITH WCL. ONLY GCC 2.1 IS KNOWN TO WORK!

Note that code compiled by gcc cannot currently be loaded into a WCL which has
been built using Sun cc because the gcc library routines are not available.

INSTALLING GCC2.1
------------------

configure sun4
<edit the Makefile and change "prefix" from /usr/local to whatever you want>
make LANGUAGES=c
make stage1
make CC=stage1/gcc CFLAGS="-g -O -Bstage1/" LANGUAGES=c
make CC=stage1/gcc install LANGUAGES=c

Just type "gcc -v" to see if gcc is installed. If it is, it will
print out the version number of the gcc you have.
After gcc is built and installed, you can delete the
entire gcc directory.

INSTALLATION PROBLEMS
---------------------

Running out of swap space is the most common installation problem.
The obvious answer is to get more space.

Another common problem is using a version of GCC other than GCC 2.1.
If you get the following message during a WCL build:

 	   WCL: Ignoring signal number 10, aborting to top-level
	   No CATCH tag found
	   <repeated over and over>

Then you are probably using a version of GCC after 2.1.


If for some reason you cannot successfully recompile WCL, then you can
use the binaries provided in the distribtion. However, you will have
to set the environment variable LD_LIBRARY_PATH to the name of the
directory containing the WCL library.

Don't worry if you see a message like:

   ld.so: warning: /usr/lib/libc.so.1.5 has older revision than expected 6

when the distributed binary starts up.  Unfortunately, the distributed
binaries do not contain debugging information, whereas the recompiled
binaries do. You will also have to compile CLX, PCL, the pretty
printer and the logical pathname code yourself if you do not perform a
full installation.

CROSS COMPILATION
-----------------

WCL can be cross compiled using Lucid Common Lisp. The resulting
binary can then be used to rebuild itself.  The src/build directory
contains some useful scripts.


