OpenMCL installation


Table of Contents

Installing OpenMCL binary/source releases for LinuxPPC and DarwinPPC

Installing OpenMCL binary/source releases for LinuxPPC and DarwinPPC

This is pretty straightforward, but there's been some confusion about this in the past, so I hope that this makes things clear.

As described in the directory hierarchynote, OpenMCL sources and binaries are intended to reside in a directory named "ccl".

OpenMCL binary releases are distributed as 'gzip'ed tar archives whose names are of the form "openmcl-PLATFORM-bin-x.y.tar.gz", where "PLATFORM" is one of "linuxppc" or "darwinppc" and "x" and "y" are major/minor version numbers. Binary releases contain:

  • the OpenMCL kernel: "ccl/ppccl" for LinuxPPC, "ccl/dppccl" for DarwinPPC

  • the OpenMCLinitial heap image: "ccl/PPCCL" for LinuxPPC, "ccl/dppccl.image" for DarwinPPC

  • ccl/README-openmcl-bin-x.y

  • ccl/scripts/openmcl

OpenMCL source releases are also distributed as 'gzip'ed tar archives whose names (not surprisingingly) are of the form "openmcl-src-x.y.tar.gz". These are archives of a checked-out copy of the OpenMCL CVS tree as of the corresponding binary release. Source releases contain:

ccl/
ccl/CVS/
ccl/CVS/Root
ccl/CVS/Repository
ccl/CVS/Entries
ccl/CVS/Entries.Log
ccl/binppc/
ccl/binppc/CVS/
ccl/binppc/CVS/Root
...
  

e.g., they're intended to create and/or populate the same ccl directory.

So, release tar.gz archives should be extracted from the directory that is or will be the parent of the

ccl directory; if you'd prefer to obtain OpenMCL sources via CVS the cvs get command should be issued from the parent directory as well. (The CVS -d option and GNU tar's -C option can also be used, but the intent is that sources and binaries wind up in the same ccl directory.)

For example, assuming that one wants to make the ccl directory be "˜/lisp/ccl":

  1. Download the binary release archive.

    > cd ~/lisp
       
  2. Do something like:

    > tar foxvz openmcl-PLATFORM-bin-x.y.tar.gz
       

That should create (or update the contents of) ˜/lisp/ccl.

You could then either (a) repeat the process with the corresponding source release archive, or (b) having done a "cvs login" to the clozure.com CVS server at some point, issue a "cvs get" from ˜/lisp.

It's possible to use the OpenMCL binaries without having installed the sources, but some functionality (like non-trivial usage of the LOOP macro) is autoloaded.

After having installed a binary release for the first time, you should consider installing the OpenMCL shell script.

It's possible (and, assuming the use of NFS or something similar, quite useful) to "share" the same directory between Linux and Darwin.

Note that binary distributions intentionally do not contain the OpenMCL interface database for either platform. The interface database files are fairly large and (ideally) fairly stable - their contents should change less frequently than the lisp itself - and are therefore distributed separately. It's necessary to install the appropriate interface database in order to compile OpenMCL sources; see here for more information.