ACL2 Version 3.2 Copyright (C) 2007 University of Texas at Austin. ACL2 is licensed under the terms of the GNU General Public License. See below for details.
Often we put timing comparisons between different lisps in the ACL2 News.
Gnu Common Lisp (GCL) has probably been the most commonly-used platform for ACL2, certainly among non-commercial Lisps. IMPORTANT: Here we are referring to the non-ANSI version (sometimes called the "CLtL1 version") of GCL. It is probably impossible to build ACL2 with ANSI GCL as of December 2005, but recent GCL advances suggest that this may be possible soon.
Debian package. You do not need to fetch GCL if you download the binary Debian package for ACL2. Thanks to Camm Maguire for maintaining this package.
GCL may be fetched from
If that site goes down, you may be able to find useful information from the GCL Temporary Distribution Site.
GCL maintainer Camm Maguire suggests the following, in order of preference
(most to least):
You may obtain recent CVS versions by executing the following commands if you have CVS installed on your system, which will retrieve the latest development/unstable cvs sources by default.
export CVS_RSH=ssh [or, if using csh: setenv CVS_RSH ssh] cvs -d:ext:email@example.com:/cvsroot/gcl co gclIf you happen to know a particular version of GCL that you wish to obtain, perhaps by following GCL mailing lists, you can replace the commands above by commands such as the following.
export CVS_RSH=ssh [or, if using csh: setenv CVS_RSH ssh] cvs -d:ext:firstname.lastname@example.org:/cvsroot/gcl co -r Version_x_y_z -d gcl-x.y.z gcl
Macintosh. Robert Krug has provided instructions for building GCL on Mac OS X, which we include here (very slightly modified, in part with help from Camm Maguire) in case others find them helpful.
The normal build process for GCL on Mac OS X assumes that you have installed fink on your Mac. (If you do not know what this is, don't worry; you probably don't have it or want it.) Here we give instructions that have worked for building GCL on OS X without fink. A. Obtain recent sources (there is a problem, e.g., with gcl-2.6.7). For example, you can do the following: export CVSROOT=:pserver:email@example.com:/sources/gcl cvs -z9 -q co -d gcl-2.6.8pre -r Version_2_6_8pre gcl At some point you may be able to obtain GCL from ftp://ftp.gnu/org/, cd gnu, cd gcl, get gcl-2.6.8.tar.gz, tar xfz gcl-2.6.8.tar.gz) B. Make sure that /usr/local/bin is in your PATH; if not, run: PATH="$PATH:/usr/local/bin" C. cd <gcl directory> D. You now need to patch file h/powerpc-macosx.defs (this might not be necessary starting with GCL 2.6.8): Replace the line: LIBS := `echo $(LIBS) | sed -e 's/-lncurses/ /'` /sw/lib/libintl.dylib With: LIBS := `echo $(LIBS) | sed -e 's/-lncurses/ /'` /usr/local/lib/libintl.dylib E. Configure and start to build gcl: ./configure make F. Install gcl: sudo make install
Obtaining Allegro Common Lisp
Allegro Common Lisp is probably the most commonly-used commercial platform for
ACL2. You may be able to obtain a trial version from its web site,
Obtaining CMU Common Lisp
CMU Common Lisp (sometimes called CMUCL) is a non-commercial Common Lisp
implementation, available from
SBCL (Steel Bank Common Lisp) is a non-commercial Common Lisp
implementation, available from
CLISP is a non-commercial Common Lisp implementation, available from
OpenMCL is a free Common Lisp implementation that runs on Macintosh OS X and
PPC Linux, and also on x86-64 OSX, Linux, and FreeBSD. It is available from
active development resulting in
that we have found useful. After
downloading, you may want to edit the file
ccl/scripts/openmcl64, depending on whether you want to use
the 32-bit or 64-bit version (respectively).
Lispworks is a commercial Common Lisp available from
Lispworks note. We initially encountered a problem in getting ACL2 to run under LIspworks 4.2.0. The Lispworks folks provided a patch and suggested that we make the following announcement.
Users with LispWorks4.2.7 should ask us at firstname.lastname@example.org for the transform-if-node patch. It will be helpful if they quote (Lisp Support Call #11372) when doing so. Also, they must send a bug form generated from their LispWorks image: instructions at http://www.lispworks.com/support/bug-report.html.
[Back to Installation Guide.]