After using Subversion to check out a copy of CCL (or unpacking an archive), you should have a directory named ccl. We will call this the "ccl directory."

Clozure CL consists of two parts: the lisp kernel, and the heap image. When the lisp kernel starts, it locates the heap image, loads it into memory, and starts running lisp code. In the ccl directory, you will find heap images and pre-compiled lisp kernel binaries for your platform.

Here are the names used for the lisp kernel on the various platforms. The heap images are named similarly, only they have a ".image" suffix.

kernel/image name platform lisp kernel build directory
lx86cl, lx86cl64Linux x86, x86-64 linuxx8632, linux8664
dx86cl, dx86cl64OS X (Darwin) x86, x86-64 darwinx8632. darwinx8664
fx86cl, fx86cl64FreeBSD x86, x86-64 freebsdx8632, freebsdx8664
sx86cl, sx86cl64Solaris x86, x86-64 solarisx86, solarisx64
wx86cl, wx86cl64Windows x86, x86-64 win32, win64
ppccl, ppccl64Linux PowerPC 32-bit, 64-bit linuxppc, linuxppc32
armclLinux ARM 32-bit (armv6) linuxarm

By default, the lisp kernel will look for a heap image in the same directory that the lisp kernel itself is in. Thus, it is possible to start CCL simply by running ./lx86cl64 (or whatever the appropriate binary is called) directly from the ccl directory.

If the lisp kernel binary does not work, you probably need to rebuild it on your local system. An error message that says somthing like "GLIBC_2.15 not found" is an indication that you need to do this. See the section below for instructions.

Running CCL

Using SLIME

If you always run CCL from SLIME, it will suffice to use the pathname of the lisp kernel binary directly. That is, in your Emacs init file, you could write (setq inferior-lisp-program "/path/to/ccl/lx86cl64") or the make the equivalent changes to slime-lisp-implementations.

Using the ccl shell script

It can also be handy to run CCL straight from a terminal prompt.

In the scripts/ directory of the ccl directory, there are two files named ccl and ccl64. Copy these files into /usr/local/bin or some other directory that is on your path, and then edit them so that the value of CCL_DEFAULT_DIRECTORY is your ccl directory. You can then start up the lisp with "ccl" or "ccl64".

You may wish to install scripts/ccl64 with the name ccl if you use the 64-bit lisp more. If you want the 32-bit lisp to be available as well, you can install scripts/ccl as ccl32.

Note that there is nothing magical about these scripts. You should feel free to edit them as desired.

Building the lisp kernel

As mentioned above, it is sometimes necessary to compile the lisp kernel binary on your local system.

To do this, from your ccl directory, go to lisp-kernel/linuxx8664 (or whatever the proper directory is for your system; see the table above), and do "make clean && make".

For example, on FreeBSD, you would do:

cd lisp-kernel/freebsdx8664  # or freebsdx8632 for the 32-bit version
make clean && make

Note that you must have m4 installed in order to compile the lisp kernel. On OS X, if you get warnings about not being able to find certain include files, run "xcode-select --install".

See the the manual for gory details about the build process.