[Openmcl-devel] save-application and mcclim

[James Ashley]

Howdy, everyone. n00b warning.

This could very well be the totally wrong list for this topic. Or
maybe it's an FAQ that I missed. Or maybe google did a horrible job
digging back through the archives. If that's the case, I apologize.
Somehow, I don't think this is the case.

I'm trying to get a ccl environment up and running on linux (yes, I
know). I got the kernel and image running (seems to be working
fine...emacs and slime seem to be perfectly happy, even if several of
the examples have issues...I figure one of the best things I can do to
learn/contribute is to figure out what those issues are and how to fix
them).

Then I installed quicklisp (I know, beta, 3rd-party, unsupported
software, bear with me), set it up to load automatically, and used it
to install climacs (*sigh*...yes, I *know*).

Up to this point, everything's working great.

climacs takes forever to load, so I did a (save-application
"whatever"). Then replaced the image file in the directory with my
kernel with that file.  Restart...no climacs.

So, I restarted with a basic image.

(defparameter *check* 9)
(save-application "whatever")

Restart emacs and slime.

*check* -> "Unbound variable *check*\n\t[Condition of type UNBOUND-VARIABLE]"

(yes, I've spent way too long in the c++ world).

The images that are being created are significantly bigger than
default supplied ones. 66666736 bytes for the "with clim" one and
28303600 bytes for the "with a dynamic variable" one, as opposed to
735459 for the original. Not that I care about that...it just seems
like it might be a symptom.

Should I switch to the 1.6 pre-release version? (That's sort of my
inclination, but I'm already feeling on the lonely side of the
bleeding edge). Am I just missing something really basic? Is there
something I could do that might offer someone else a clue about where
the problem lies (especially if it's PEBKAC) that might point me in
the correct direction? Should I switch back to SBCL until I'm not so
clueless? Break down and switch to Windows (uggh)? (Right now, a Mac
just isn't in the budget).

Thanks in advance,
James