[Openmcl-devel] Rebuilding CCL
millejoh at mac.com
Thu Jun 18 10:24:47 PDT 2009
I find that doing a (require "COCOA-APPLICATION") from the command-
line always works for me. Whenever I update from the IDE, however,
the next time a restart I get an error in Hemlock (which I promise to
make ticket for the next time it happens. Honest. Scout's honor.).
I've been building from the trunk for many months and had almost no
problems doing this. You might want to try doing this instead trying
to update using the 1.3 DMG file as I do not think that set of files
follows the trunk. Note that my version of CCL says "Welcome to
Clozure Common Lisp Version 1.4-dev-r12265M-trunk (DarwinX8664)!"
On Jun 18, 2009, at 11:53 AM, Tim Bradshaw wrote:
> Sorry, a followup question to the one I asked just now.
> How do you rebuild the Cocoa IDE?
> What I've done:
> - Fetched the original 1.3 .DMG file. The IDE works fine in this (so
> the various *.app things there are fine).
> - Discovered that, in fact, "svn update" works for this. Did that
> - rebuilt the command-line application using (ccl:rebuild-ccl :full
> t). This works fine
> - Now try ccl -e "(require :cocoa-application)". This builds an
> application bundle, but when you run it spits out a lot of noise about
> compiling & loading stuff into the listener, and then ends up in a
> break loop.
> If I run the command-line application (which claims to be "1.3-
> r12265M (Darwinx8632)" now), and do a (require "COCOA"), this does
> start the IDE, but each time you run it it compiles a lot of stuff.
> That smells bad to me - is there some issue with file-dates which I do
> not understand?
> I'm using an x86(-64) MacBook, running 10.5.7, patched to date.
> It may be that the answer is "the current version does not build" and
> I should just go back to the DMG one and not try and update/rebuild
> it: that would be fine, though it's kind of nice to be able to rebuild
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel