Installing CDL3 is not very tested yet. But it should work this way:

 - run configure, for example: ./configure --prefix=/usr/local/cdl3
 - run make, which should compile stage zero and one, and the runtime
   system.
 - run "make install" to install the binaries, runtime system and
   include files.

Note: don't run a parallel make (make -j) because this will mess up the
compilation process done by cdlc in stage1 (this is a problem with
automake, it seems).

As CDL3 is written in CDL3, you cannot compile those CDL3 sources on any
system without a CDL3 compiler.  Therefore in stage0 a version in C
(which has been generated from the actual CDL3 source files) is build.
Stage 1 uses the compiler build in stage 0 to compile the actual CDL3
sources.

At this moment only the C backend is known to build this way.
The i386 and Sparc backends do can be build by replacing the links in
the stage1 directory to point to the appropriate coder.K3 files (note
the capital K, this means that this file should be preprocessed by cpp).
But there is a problem with the i386 code generator on Linux with recent
binutils: it seems that some portions of the memory are initiated wrong.
The Sparc version might also have this problem, but it is only tested on
SunOS (nearly all versions from 4.1.x to 5.7) and seems to work.

-- Erik Verbruggen (ejv@cs.kun.nl)
