[Openmcl-devel] trunk bootstrapping

Gary Byers gb at clozure.com
Thu Jul 9 04:27:03 PDT 2009

As of r12394, it should be OK to use the trunk again.

There are new binaries (kernels and .image files) for all (14 ...) platforms
in svn.  New kernels won't work with old images and vice versa, so it's
important to pick up the new versions of these files when doing an 'svn update';
one way of ensuring that this happens is to remove or rename your local copies
of the kernel and .image files before updating.

The FASL file version has also changed; old FASL files won't work with this
lisp image and vice versa.

The changes are relatively minor: some stuff intended to allow much larger
compiled functions on 32-bit X86 platforms, the Japanese character encodings
from Yoshinori Tahara, an alleged fix for ticket 554 (GC deadlock).  The
first set of changes pretty much necessitated the FASL and image version
changes (at least on 32-bit x86), and there have been some other cases where
we've introduced small binary incompatibilities and have been casual about
ensuring that kernel/image/fasl versions are in synch, so this seemed like
a good time to synchronize again.

On Wed, 8 Jul 2009, Gary Byers wrote:

> Some changes that'll be committed to the trunk soon are hard to bootstrap;
> people who use the trunk should probably avoid updating from it until
> this round of changes is complete.
> (That'll probably be less than a day, knock wood.)
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

More information about the Openmcl-devel mailing list