[Openmcl-devel] trunk changes
gb at clozure.com
Wed Dec 9 22:32:38 UTC 2009
OK, trunk sources have been updated and binaries for all platforms have been
checked in to the trunk. If you track the trunk and want to be able to
rebuild your working copy:
- you'll need to use the new binaries (kernel/.image files) that were just
- you'll need to be aware of the fact that 'svn up' generally won't update
working copies of binary files that appear to have been locally modified.
There are several ways of dealing with the second issue:
- if run interactively, svn 1.5 or later will ask for advice when it
encounters a binary file which has changed locally and for which a
new version is available in the repository. The appropriate response
is 'tf' ("theirs full")
- with all versions of svn, it's possible to "revert" conflicting binaries
to the repository version by doing:
shell> cd ccl
shell> svn revert -R .
(Note the trailing "." in the previous line.)
- with relatively recent versions of CCL, (rebuild-ccl ... :update t) will
try to do the "svn update" for you and will revert conflicting binaries;
if it needs to do this step, it'll advise you to quit the current lisp
and use the new binaries to rebuild your working copy.
The FASL version changed, as did the version numbers that keep images and
kernels in synch with each other.
The changes are (mostly) not user-visible: they mostly have to do with
how the lisp manages its address space (allowing SAVE-APPLICATION to
copy most x86 functions to an area of memory that's not scanned by the
GC; the PPC port has always done this) and with how string constants
are stored in FASL files.
On Wed, 9 Dec 2009, Gary Byers wrote:
> I have a bunch of code that I need to check in to the trunk over the next day
> or so. The changes will introduce bootstrapping problems, so I'll check in
> new binaries for all platforms once I'm done.
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel