[Openmcl-devel] new trunk binaries

[Gary Byers]

I just finished committing new binaries for all platforms to the trunk.

A bug was introduced a few days ago (in r13497) that mostly affected 32-bit
x86 and caused SAVE-APPLICATION to produce corrupt images; there's a slim
chance that 64-bit x86 could also have been affected (the PPC ports weren't.)
If you've updated from svn in the last few days and have gotten wedged, using
the newer binaries is one way to get unwedged.

Otherwise, the new binaries are just there because they match current trunk
sources (and will until those sources start to diverge) and can currently
build the lisp from those sources without warnings or CERRORS.  There aren't
any low-level ABI changes or dependencies between kernel and image in this
case, so if "svn up" leaves you with a locally-modified fairly recent image
and a kernel from the repository (or vice versa) things should work (as long
as you weren't affected by the r13497 bug.)

If you were affected by that bug, you can get un-wedged by either:

a) following the steps that Rafael Cavallaro described in:

<http://clozure.com/pipermail/openmcl-devel/2010-March/011313.html>

b) doing:

$ cd ccl
$ svn up
$ svn revert -R .

to ensure that local copies of the kernel and image match the versions in
the repository, then using those new binaries to rebuild as usual.