As of this writing, Clozure CL 1.4 is the latest release; it was - made in October 2009. For up-to-date information about releases, +
As of this writing, Clozure CL 1.7 is the latest release; it was + made in August 2011. For up-to-date information about releases, please see http://ccl.clozure.com/.
-Clozure CL runs on the following platforms:
+Clozure CL 1.7 runs on the following platforms:
Linux (x86, x86-64, ppc32, ppc64)
+Linux (x86, x86-64, ppc32, ppc64, armv7)
Mac OS X 10.4 and later (x86, x86-64, ppc32, ppc64)
+Mac OS X 10.5 and later (x86, x86-64)
Naturally, 64-bit versions of Clozure CL require 64-bit processors, + for example, a G5 or Core 2. Some early Intel-based Macintoshes + used processors that don't support + 64-bit operation, so the 64-bit Clozure CL will not run on them, although + the 32-bit Clozure CL will. +
+ +The 32-bit x86 versions of Clozure CL depend on the presence of the SSE2 instructions. + Most x86 processors manufactured and sold in the last several years support SSE2 (all Apple Intel-based Macs do, for instance), + but there are some exceptions. + The Wikipedia article on SSE2 lists processor models that support SSE2 + (and also mentions some of the more notable exceptions). +
+The Linux ARM port is relatively new and is still a work-in-progress. + Clozure CL +needs some features (such as hardware floating-point, locking and +memory-serialization primitives) that are only found in chips +that implement architecture version 7 (ARMv7); technically, it needs +the ARMv7 "application profile", which is sometimes called ARMv7a. + +In practice, most ARM consumer devices released in the last few +years implement ARMv7, but there are exceptions, and it is +not practical to enumerate all of the ARM devices that CCL should +run on. +
++In addition to hardware issues, Clozure CL expects Linux to run in little-endian +mode and expects software to follow "soft float" calling conventions. +The latter has to do with how C functions accept floating-point arguments +and return floating-point values. + +
+Clozure CL runs under Mac OS X versions 10.4 and later. Post-1.4 - versions will require at least 10.5. +
Clozure CL 1.7 runs on Mac OS X (x86) versions 10.5 and later, including 10.7 (Lion),
-64-bit versions of Clozure CL naturally require 64-bit processors - (e.g., a G5 or Core 2 processor). Some early Intel-based Macintoshes - used processors that don't support - 64-bit operation, so the 64-bit Clozure CL will not run on them, although - the 32-bit Clozure CL will. -
+Clozure CL 1.6 runs on Mac OS X PPC as well as x86 processors.
-There two main ways to obtain Clozure CL. For Mac OS X, +
There are three ways to obtain Clozure CL. For Mac OS X, there are disk images that can be used to install Clozure CL in the usual Macintosh way. For other OSes, Subversion is the best @@ -1161,6 +1238,7 @@
There are three popular ways to use Clozure CL: as a stand-alone double-clickable application (Mac OS X only), as a - command-line application, or with Emacs and SLIME. The following - sections describe these options.
+ command-line application, or with Emacs and SLIME. + +The following sections describe these options.
So that Clozure CL can locate its source code, and for other reasons explained in @@ -1195,10 +1273,26 @@
-It is very easy to download, install, and build Clozure CL - using Subversion. This is the preferred way to get either the +
Tarball distributions of Clozure CL release version 1.7 are available at + ftp://clozure.com/pub/release/1.7/. + Download and extract + one on your local disk. Then edit the Clozure CL shell script to set + the value of CCL_DEFAULT_DIRECTORY and start + up the appropriate Clozure CL kernel. See Section 2.3.1, âThe ccl Shell Scriptâ for more information about the + Clozure CL shell scripts.
+ +It is very easy to download and configure Clozure CL to obtain sources from the Subversion repository. + This is the preferred way to get either the latest, or a specific version of Clozure CL, unless you prefer the Mac Way. Subversion is a source code control system that is @@ -1207,121 +1301,25 @@ sources and binaries can be retrieved with a single Subversion command.
-Day-to-day development of Clozure CL takes place in an area - of the Subversion repository known as the trunk. At most times, - the trunk is perfectly usable, but occasionally it can be unstable - or totally broken. If you wish to live on the - bleeding edge, the following command will fetch a copy of the trunk - for Darwin x86 (both 32- and 64-bit versions): -
-- -svn co http://svn.clozure.com/publicsvn/openmcl/trunk/darwinx86/ccl --
- To get a trunk Clozure CL for another platform, replace - "darwinx86" with one of the following names (all versions - include both 32- and 64-bit binaries): -
-darwinx86
-linuxx86
-freebsdx86
-solarisx86
-windows
-linuxppc
-darwinppc
-Release versions of Clozure CL are intended to be stable. While - bugs will be fixed in the release branches, enhancements - and new features will go into the trunk. To get the 1.4 release - of Clozure CL type:
-- -svn co http://svn.clozure.com/publicsvn/openmcl/release/1.4/darwinx86/ccl --
The above command will fetch the complete sources and binaries - for the Darwin x86 build of Clozure CL. To get a Clozure CL for another platform, - replace "darwinx86" with one of the following names (all versions - include both 32- and 64-bit binaries):
-darwinx86
-linuxx86
-freebsdx86
-solarisx86
-windows
-linuxppc
-darwinppc
-These distributions contain complete sources and - binaries. They use Subversion's "externals" features to share - common sources; the majority of source code is the same across - all versions.
-Once the checkout is complete you can build Clozure CL by
- running the lisp kernel and executing
- the rebuild-ccl function. For
- example:
- -joe:ccl> ./dx86cl64 -Welcome to Clozure Common Lisp Version 1.2 (DarwinX8664)! -? (rebuild-ccl :full t) - -<lots of compilation output> - - ? (quit) - joe:ccl> --
- If you don't have a C compiler toolchain installed,
- rebuild-ccl will not work. Please
- refer to Chapter 3, Building Clozure CL from its Source Code for
- addtional details.
-
Unless stated otherwise, examples in this chapter are given for Mac OS X in particular + or Unix-based host environments in general. +
+For Windows, special care must be taken to install a working development environment. + For more information see the Clozure CL Wiki at URL: http://trac.clozure.com/ccl/wiki/WindowsNotes +
+If svn co doesn't work, then make sure
- that Subversion is installed on your system. Bring up a command
+
Make sure that Subversion is installed on your system. Bring up a command line shell and type:
-
shell> svn
@@ -1330,5 +1328,4 @@
-
Type 'svn help' for usage
@@ -1338,5 +1335,4 @@
-
-bash: svn: command not found
@@ -1345,6 +1341,119 @@
to install it on your OS. You can find information about
obtaining and installing Subversion at
- the Subversion
- Packages page.
+ the Subversion
+ web page.
+ Before you download Clozure CL you should consider: + Do you want to run the most recent source code, or the current stable release version? + If you don't know how to answer this question, then you probably want the release version. +
+Day-to-day development of Clozure CL takes place in an area + of the Subversion repository known as "the trunk". At most times, + the trunk is perfectly usable, but occasionally it can be unstable + or totally broken. + If you wish to live on the bleeding edge, download sources from the trunk. +
+For example, the following command will fetch a copy of the trunk + for Mac OS X (Darwin) with x86 processors (both 32- and 64-bit versions): +
+svn co http://svn.clozure.com/publicsvn/openmcl/trunk/darwinx86/ccl ++
+ To get a trunk Clozure CL for another platform, replace + "darwinx86" with one of the following names (all versions + include both 32- and 64-bit binaries): +
+darwinx86
+linuxx86
+freebsdx86
+solarisx86
+windows
+linuxppc
+darwinppc
+Release versions of Clozure CL are intended to be stable. While + bugs will be fixed in the release branches, enhancements + and new features will go into the trunk. + If you wish to run the stable release, + the following command will fetch a copy of the release version 1.7 + for Mac OS X (Darwin) with x86 processors (both 32- and 64-bit versions): +
+svn co http://svn.clozure.com/publicsvn/openmcl/release/1.7/darwinx86/ccl ++
To get the release version of Clozure CL for another platform, + replace "darwinx86" with one of the following names: +
+darwinx86
+linuxx86
+freebsdx86
+solarisx86
+windows
+linuxppc
+darwinppc
+These distributions contain complete sources and + binaries. They use Subversion's "externals" features to share + common sources; the majority of source code is the same across + all versions.
+Tarballs are available at ftp://clozure.com/pub/release/1.4/. Download and extract - one on your local disk. Then edit the Clozure CL shell script to set - the value of CCL_DEFAULT_DIRECTORY and start - up the appropriate Clozure CL kernel. See Section 2.3.1, âThe ccl Shell Scriptâ for more information about the - Clozure CL shell scripts.
+This section explains how to peform a "full rebuild" of Clozure CL from a source distribution.
+After downloading Clozure CL sources, you should rebuild Clozure CL as described here.
+ At the start of a full rebuild, object files in the ccl directory are deleted,
+ which causes the build script to recompile the runtime kernel (C code) and high-level sources (Lisp),
+ then save a new heap image.
+ Doing a full rebuild helps to ensure that your local installation will run properly for your host OS environment.
+
In an interactive shell, a command sequence like the following will rebuild Clozure CL in place: + +
++joe> cd+/path/to/installed/ccl+joe:ccl> ./kernel-filename--no-init +Welcome to Clozure Common Lisp Version [...] +? (rebuild-ccl :full t) +<...lots of compilation output...> +? (quit) +joe:ccl> +
+
+Replace /path/to/installed/ccl with the path of the ccl directory
+ that you downloaded.
Replace kernel-filename with the filename of the Lisp kernel program.
+ To find the filename of a Lisp kernel image for your particular platform, see Section 3.1.1, âPlatform-specific filename conventionsâ.
+
The rest of this section covers the following topics in brief: +
++
+This section does not provide comprehensive documentation on the build process. + Please refer to Chapter 3, Building Clozure CL from its Source Code for more information. + Those more detailed instructions are used mainly by developers who maintain, customize, and/or port Clozure CL. + If you are customizing Clozure CL, or if you run into some exceptional situation, + you may need to perform the individual build steps. +
+In order to build Clozure CL you must have a working system and development environment.
+ There are different requirements and setup procedures for each platform, but the main requirement is to have
+ a C compiler and a few other utilities:
+ GNU gcc or cc with ld and as;
+ make; and m4.
+ Please refer to Chapter 3, Building Clozure CL from its Source Code for details.
+
If you don't have the prerequisite C compiler toolchain installed, rebuild-ccl will not work.
+ See Section 3.3, âKernel Build Prerequisitesâ for additional details.
+
Most distributions of Linux have all or most of the required development tools either pre-installed + or readily available. + On Debian-based Linux you can download and install the essential build tools using the package manager. + For example:
+apt-get install build-essential+
+ (You may need to install C header files separately.) +
+For Mac OS X, Xcode 4 is available from the App Store.
+For Windows, follow the procedure outlined in the Clozure CL Wiki + at URL: http://trac.clozure.com/ccl/wiki/WindowsNotes +
+The most common scenario that requires a full rebuild is the standard installation after downloading the source tree. + Users and application developers (who otherwise have no special build requirements) + will generally need to run the full rebuild process just once + for any given installation on a particular host system. +
+Another common scenario is installing a patch update:
+ You can use Subversion (svn update) to download a more recent set of source files.
+ (Be sure to download sources from the same path and branch in the source repository.)
+ Then run a full rebuild to create new kernel and heap images.
+ If you are running Clozure CL from the trunk, you may need to update sources and run the full rebuild more often.
+
Another reason to do a full rebuild is to ensure that Clozure CL will run properly in the host OS environment. + This may be necessary, for example, when the target OS version + is not identical to the one where the pre-built kernel was generated. + The Lisp kernel uses some functionality defined in standard platform-provided libraries. + On some platforms, applications (such as the Lisp kernel) are built in + such a way as to depend on the specific versions of these libraries that were + present at build time, and may not run on systems that have older or newer versions + of these libraries. + If you're affected by this, the simplest workaround is to build the Lisp kernel + on the machine(s) that you intend to run it on and use that locally-built kernel instead of one distributed via Subversion. +
+Once the checkout is complete, and provided that you have a working development setup, + you can build Clozure CL by running the Lisp kernel (an OS-native executable program) + and running REBUILD-CCL in Lisp. +
+For example, to build a 64-bit Clozure CL on Mac OS X: + +
++joe:ccl> ./dx86cl64 --no-init +Welcome to Clozure Common Lisp Version 1.7 (DarwinX8664)! +? (rebuild-ccl :full t) +Rebuilding Clozure Common Lisp using Version 1.7 (DarwinX8664) +;Building lisp-kernel ... +;Kernel built successfully. +;Compiling <...> +;Loading <...> + +<...lots of compilation output...> + +;Wrote bootstrapping image: #P"/Users/joe/ccl/x86-boot64.image" +;Wrote heap image: #P"/Users/joe/ccl/dx86cl64.image" +NIL +? (quit) +joe:ccl> ++
+
+If the build fails for any reason, the kernel and/or heap image files may be missing or corrupted. + To recover, delete the image files and update the source directory from Subversion. + For example: + +
++joe:ccl> rm dx86cl* +joe:ccl> svn update +<... lots of Subversion output...> +joe:ccl> ./dx86cl64 --no-init +Welcome to Clozure Common Lisp Version 1.7 (DarwinX8664)! +? (rebuild-ccl :full t) +<... lots of compilation output...> +? (quit) +joe:ccl> + ++
+ Follow this same procedure to perform the fuil rebuild from scratch, for example
+ in the case where the saved Lisp image contains code that was loaded inadvertently.
+ (Classic mistake: forgetting to specify the --no-init command option.)
+
Once the full rebuild is completed, you can run the new Lisp kernel from the command shell.
+ However, running the OS- and processor-specific executable directly is not recommended
+ for day-to-day use.
+ Clozure CL includes the ccl and ccl64 command shell scripts.
+ For details on configuring a shell script for your environment, see Section 2.3.1, âThe ccl Shell Scriptâ.
+
Should the build fail, your first concern should be to confirm that all requirements are in place: + the C compiler, utilities, and OS header files; + source files for the trunk or release branch you want to build; + and the Lisp kernel and heap image files. + For assistance with trouble-shooting, here is an outline of the full build process, + with links to the more detailed instructions in Chapter 3, Building Clozure CL from its Source Code. +
+Build the Lisp kernel (Section 3.5, âBuilding the Kernelâ)
+Build the heap image (Section 3.6, âBuilding the Heap Imageâ)
+Create a bootstrapping heap image (Section 3.6.2, âGenerating a bootstrapping imageâ)
+Compile Lisp code to generate fasl files (Section 3.6.3, âGenerating fasl filesâ)
+Build a full image from bootstrapping image + (Section 3.6.4, âBuilding a full image from a bootstrapping imageâ)
+Run new kernel with new bootstrapping image
+Load Lisp code
+Save a new full heap image
++
+"ccl/scripts/ccl64" is used to invoke
- 64-bit implementations.
+ 64-bit implementations.
+ Install one script or the other or both as needed.
+
To use the script:
ccl directory. Alternately, set
the value of the CCL_DEFAULT_DIRECTORY
- environment variable in your .cshrc, .tcshrc,
- .bashrc,.bash_profile, .MacOSX/environment.plist, or
- wherever you usually set environment variables. If there
- is an existing definition of the variable, the ccl
+ environment variable
+ wherever you usually set per-user environment variables, in your
+ .cshrc, .tcshrc,
+ .bashrc, .bash_profile,
+ or .MacOSX/environment.plist script,
+ or system-wide in /etc/profile or /etc/bashrc.
+ When the ccl script runs, if the process environment contains
+ a definition of CCL_DEFAULT_DIRECTORY, the ccl
script will not override it.
@@ -1474,14 +1831,20 @@
Once this is done, it should be possible to invoke Clozure CL
by typing ccl
- or ccl64 at a shell prompt:
ccl64 at a shell prompt:
+
+
-> ccl [args ...]
-Welcome to Clozure CL Version 1.2 (DarwinPPC32)!
+shell> ccl
+Welcome to Clozure Common Lisp Version 1.7 (DarwinX8632)!
?
+ +
The ccl shell script passes all of its arguments to the
Clozure CL kernel. See Section 2.3.2, âInvocationâ for more
- information about these arguments. When invoked this way, the
- Lisp should be able to initialize the "ccl:"
+ information about command-line arguments.
+
Assuming the shell script is configured and invoked properly, Clozure CL
+ should be able to initialize the "ccl:"
logical host so that its translations refer to the
"ccl" directory. To test this, you can call
@@ -1490,5 +1853,5 @@
? (probe-file "ccl:level-1;level-1.lisp") ;returns the physical pathname of the file
-#P"/Users/alms/my_lisp_stuff/ccl/level-1/level-1.lisp"
+#P"/Users/joe/my_lisp_stuff/ccl/level-1/level-1.lisp"
Assuming that the shell script is properly installed, it can be used to invoke Clozure CL from a shell prompt:
-
-shell>ccl args
-
+ shell>ccl[args ...]
+ By convention
ccl runs a 32-bit session;
ccl64 runs a 64-bit session.
+ However, the name of the installed script(s) and the implementation that is invoked are customizable,
+ as described in Section 2.3.1, âThe ccl Shell Scriptâ.
For details about command-line options see + Section 2.5, âCommand Line Optionsâ. +
@@ -1677,5 +2044,5 @@ Finally, any arguments following the pseudo-argument-- are not processed, and are made
- available to the lisp as the value of
+ available to Lisp as the value of
ccl:*unprocessed-command-line-arguments*.
@@ -1761,10 +2128,15 @@
The following terms are used in subsequent sections; it may be helpful to refer to these definitions.
-fasl
+ fasl
files are the object files produced
by The Lisp
+ The Lisp
kernel is a C program with a fair amount of
platform-specific assembly language code. Its basic job is to
@@ -1866,5 +2233,5 @@
files on different platforms; see
Table 3.1, âPlatform-specific filename conventionsâ. A heap
+ A heap
image is a file that can be quickly mapped into a
process's address space. Conceptually, it's not too different
@@ -1877,5 +2244,5 @@
standard full heap image files on different platforms; see
Table 3.1, âPlatform-specific filename conventionsâ. A bootstrapping image is a minimal
+ A bootstrapping image is a minimal
heap image used in the process of building Clozure CL itself. The
bootstrapping image contains just enough code to load the rest
@@ -1889,5 +2256,5 @@
as-yet-unsupported ones) has a uniquely named subdirectory of
- For example, to get a released version (1.3 in this example),
+ For example, to get a released version (1.7 in this example),
use a command like:
- Change the "xxx" to one of the following names:
+ Change the
- In the case of released versions, there may also be tar archives
- available. See the Clozure CL
- Trac for details.
+ Tarball distributions of released versions are also available for download via ftp from:
+ ftp://clozure.com/pub/release/.
+ For additional information about availability of source and distributions see the
+ Clozure CL Trac.
Subversion client programs are pre-installed on Mac OS X 10.5 and
later and are typically either pre-installed or readily available
- on Linux and FreeBSD platforms. The Subversion web page contains links to subversion client programs
- for many platforms; users of Mac OS X 10.4 can also
- install Subversion clients via Fink or MacPorts. The Clozure CL kernel can be built with the following widely
+ available tools: cc or gcc â the GNU C compiler ld â the GNU linker m4 or gm4 â the GNU m4 macro processor as â the GNU assembler (version 2.10.1 or later) make â either GNU make or, on FreeBSD, the default BSD make program In general, the more recent the versions of those
+ tools, the better; some versions of gcc 3.x on Linux have
+ difficulty compiling some of the kernel source code correctly
+ (so gcc 4.0 should be used, if possible.) On Mac OS X, the
+ versions of the tools distributed with Xcode should work fine;
+ on Linux, the versions of the tools installed with the OS (or
+ available through its package management system) should work
+ fine if they're "recent enough". On FreeBSD, the installed
+ version of the In order to build the lisp kernel on Mac OS X
+ 10.6 Snow Leopard, you must install the optional 10.4
+ support when installing Xcode. Runs another external process, which causes the newly
compiled lisp kernel to load the new bootstrapping image.
- The bootsrtrapping image then loads the âhigher
+ The bootstrapping image then loads the âhigher
levelâ fasl files and a new copy of the platform's
full heap image is then saved. The Clozure CL kernel can be bult with the following widely
- available tools: cc or gcc- the GNU C compiler ld - the GNU linker m4 or gm4- the GNU m4 macro processor as - the GNU assembler (version 2.10.1 or later) make - either GNU make or, on FreeBSD, the default BSD make program In general, the more recent the versions of those
- tools, the better; some versions of gcc 3.x on Linux have
- difficulty compiling some of the kernel source code correctly
- (so gcc 4.0 should be used, if possible.) On Mac OS X, the
- versions of the tools distributed with Xcode should work fine;
- on Linux, the versions of the tools installed with the OS (or
- available through its package management system) should work
- fine if they're "recent enough". On FreeBSD, the installed
- version of the In order to build the lisp kernel on Mac OS X
- 10.6 Snow Leopard, you must install the optional 10.4
- support when installing Xcode. Given a bootstrapping image and a set of up-to-date fasl
files, the development cycle usually involves editing lisp
- sources (or updating those sources via cvs update),
+ sources (or updating those sources via then calling This function compiles the lisp sources in the ccl/level-0
+ This function compiles the lisp sources in the Where
-
+
TRACE {
-
+
CCL:*TRACE-LEVEL* [Variable]
Variable bound to the current nesting level during execution of before and after trace actions. The default printing actions use it to determine the amount of indentation.
-
+
CCL:*TRACE-MAX-INDENT* [Variable]
The default before and after print actions will not indent by more than the value of ccl:*trace-max-indent* regardless of the current trace level.
-
+
CCL:TRACE-FUNCTION
-
+
CCL:*TRACE-PRINT-LEVEL* [Variable]
-
+
CCL:*TRACE-PRINT-LENGTH* [Variable]
-
+
CCL:*TRACE-BAR-FREQUENCY* [Variable]
@@ -3330,5 +3698,5 @@
@@ -3369,5 +3737,5 @@
@@ -3541,5 +3909,5 @@
The value of this variable is used when :EXTERNAL-FORMAT is
@@ -3567,5 +3935,5 @@
The value of this variable is used when an external-format
@@ -3599,5 +3967,5 @@
domain---This is used to indicate where the external
@@ -3633,5 +4001,5 @@
Despite the function's name, it doesn't necessarily create a
@@ -3806,5 +4174,5 @@
@@ -4392,5 +4760,5 @@
@@ -4441,5 +4809,5 @@
@@ -4494,5 +4862,5 @@
Clozure CL sets up logical pathname translations for logical hosts: The
@@ -4653,5 +5021,5 @@
@@ -4776,5 +5144,5 @@
platforms.
-
+
CCL:MAP-FILE-TO-IVECTOR
-
+
CCL:UNMAP-IVECTOR
-
+
CCL:MAP-FILE-TO-OCTET-VECTOR
-
+
CCL:UNMAP-OCTET-VECTOR
Clozure CL provides the
function As of Clozure CL 1.2, the constant
-
+
SAVE-APPLICATION
@@ -5317,5 +5685,5 @@
@@ -5364,5 +5732,5 @@
@@ -5422,5 +5790,5 @@
@@ -5596,5 +5964,5 @@
@@ -5630,5 +5998,5 @@
@@ -5716,5 +6084,5 @@
@@ -6047,5 +6415,5 @@
@@ -6069,5 +6437,5 @@
@@ -6095,5 +6463,5 @@
@@ -6121,5 +6489,5 @@
@@ -6152,5 +6520,5 @@
@@ -6179,5 +6547,5 @@
@@ -6202,5 +6570,5 @@
@@ -6226,5 +6594,5 @@
@@ -6253,5 +6621,5 @@
@@ -6280,5 +6648,5 @@
@@ -6447,5 +6815,5 @@
@@ -6473,5 +6841,5 @@
@@ -6507,5 +6875,5 @@
@@ -6552,5 +6920,5 @@
@@ -6603,5 +6971,5 @@
@@ -6628,5 +6996,5 @@
@@ -6704,5 +7072,5 @@
@@ -6739,5 +7107,5 @@
@@ -6770,5 +7138,5 @@
@@ -6795,5 +7163,5 @@
@@ -7028,5 +7396,5 @@
-
+
BUILD-APPLICATION &key
( Alternatively, you could use the standard features of
@@ -7960,5 +8328,5 @@
@@ -7982,5 +8350,5 @@
@@ -8009,5 +8377,5 @@
@@ -8053,5 +8421,5 @@
@@ -8077,5 +8445,5 @@
@@ -8100,5 +8468,5 @@
@@ -8125,5 +8493,5 @@
@@ -8150,5 +8518,5 @@
@@ -8236,5 +8604,5 @@
@@ -8258,5 +8626,5 @@
@@ -8280,5 +8648,5 @@
@@ -8303,5 +8671,5 @@
@@ -8325,5 +8693,5 @@
@@ -8349,5 +8717,5 @@
@@ -8373,5 +8741,5 @@
@@ -8428,5 +8796,5 @@
@@ -8453,5 +8821,5 @@
@@ -8476,5 +8844,5 @@
@@ -8499,5 +8867,5 @@
@@ -8539,5 +8907,5 @@
@@ -8562,5 +8930,5 @@
@@ -8585,5 +8953,5 @@
@@ -8608,5 +8976,5 @@
@@ -8651,5 +9019,5 @@
@@ -8696,5 +9064,5 @@
@@ -8740,5 +9108,5 @@
@@ -8765,5 +9133,5 @@
@@ -8820,5 +9188,5 @@
@@ -8844,5 +9212,5 @@
@@ -8866,5 +9234,5 @@
@@ -8890,5 +9258,5 @@
@@ -8914,5 +9282,5 @@
@@ -8957,5 +9325,5 @@
@@ -8981,5 +9349,5 @@
@@ -9023,5 +9391,5 @@
@@ -9046,5 +9414,5 @@
@@ -9069,5 +9437,5 @@
@@ -9095,5 +9463,5 @@
@@ -9208,5 +9576,5 @@
@@ -9231,5 +9599,5 @@
@@ -9255,5 +9623,5 @@
@@ -9278,5 +9646,5 @@
@@ -9302,5 +9670,5 @@
@@ -9326,5 +9694,5 @@
@@ -9351,5 +9719,5 @@
@@ -9376,5 +9744,5 @@
@@ -9400,5 +9768,5 @@
@@ -9425,5 +9793,5 @@
@@ -9452,5 +9820,5 @@
@@ -9475,5 +9843,5 @@
@@ -9497,5 +9865,5 @@
@@ -9529,5 +9897,5 @@
@@ -9606,5 +9974,5 @@
@@ -9628,5 +9996,5 @@
@@ -9674,5 +10042,5 @@
@@ -9700,5 +10068,5 @@
@@ -9747,5 +10115,5 @@
@@ -9772,5 +10140,5 @@
@@ -9795,5 +10163,5 @@
@@ -9819,5 +10187,5 @@
compile-file. fasl files store the
@@ -1856,5 +2223,5 @@
see
Table 3.1, âPlatform-specific filename conventionsâ ccl/lisp-kernel/; each such
-
+
contains a Makefile and may contain some auxiliary files (linker
scripts, etc.) that are used to build the lisp kernel on a
@@ -2074,10 +2441,8 @@
the Subversion source control system.
- svn co http://svn.clozure.com/publicsvn/openmcl/release/1.3/xxx/ccl
-
+ svn co http://svn.clozure.com/publicsvn/openmcl/release/1.7/
xxx/ccl
- svn co http://svn.clozure.com/publicsvn/openmcl/trunk/xxx/ccl
-
+ svn co http://svn.clozure.com/publicsvn/openmcl/trunk/
xxx/cclxxx to one of the following names:
darwinx86,
linuxx86,
freebsdx86,
solarisx86,
- window,
+ windows,
linuxppc,
or
@@ -2102,13 +2465,18 @@
apt-get install subversion or equivalent in the command-line or interactive package manager.
+
+
+ m4 program doesn't support
+ some features that the kernel build process depends on; the
+ GNU version of the m4 macroprocessor (called
+ gm4 on FreeBSD) should be installed.
+ Note
+
-
- m4 program doesn't support
- some features that the kernel build process depends on; the
- GNU version of the m4 macroprocessor (called
- gm4 on FreeBSD) should be installed.
- Note
- svn update),
recompiling modified files, and using the bootstrapping image
to produce a new heap image.ccl:xload-level-0 at the
- lisp prompt
? (ccl:xload-level-0)
- ccl/level-0
directory if they're newer than the corresponding fasl files
and then loads the resulting fasl files into a simulated lisp
@@ -2411,5 +2779,5 @@
whenever your existing boot image is out-of-date with respect
to the source files in ccl:level-0;
- :
? (ccl:xload-level-0 :force)
@@ -2421,5 +2789,5 @@
@@ -2454,5 +2822,5 @@
$ cd ccl # wherever your ccl directory is
-$ ./KERNEL BOOT_IMAGE
+$ ./
KERNEL BOOT_IMAGE
KERNEL and
@@ -2475,5 +2843,5 @@
can in the environment provided by a "real" heap image. If
you're confident that things loaded OK, you can save that
- image.
? (ccl:save-application "
image_name") ; Overwiting the existing heap image
@@ -2723,5 +3091,5 @@
keyword
global-value}* {spec |
@@ -3167,15 +3535,15 @@
spec &key {keyword value}* [Function]
ccl and homeCCL logical host should point to the
ccl directory. It is used for a variety of
@@ -4603,5 +4971,5 @@
pathname
@@ -4836,5 +5204,5 @@
a memory error.displaced-array
@@ -4848,5 +5216,5 @@
target is an empty vector (of length zero).pathname
@@ -4858,5 +5226,5 @@
bytes.displaced-array
@@ -4897,5 +5265,5 @@
static.CCL:SAVE-APPLICATION, which creates a file
@@ -5031,5 +5399,5 @@
converted, because address 0 can always be relied upon to refer to
the same thing.CCL:+NULL-PTR+
refers to a MACPTR object that points to address 0.ccl64 script.
filename
@@ -5243,5 +5611,5 @@
name "MyApplication")
@@ -7418,5 +7786,5 @@
of make for Lisp, and is included in the
Clozure CL distribution. You can read more about ASDF at the ASDF
- home
+ home
page.