cl-launch and openmcl

Dear bug-openmcl'ers,

prompted by Henrik Hjelte, I made a new pass at getting cl-launch to
work with openmcl, now trying with the x86_64 snapshot (since I do
have a x86_64 machine but no easy access to a ppc machine). The
cl-launch 1.80 automated tests worked with openmcl, but I still have
the following issues:

* When trying to dump an image, I get the following error which I
believe is an internal bug in openmcl:

> Error: value -2 is not of the expected type (UNSIGNED-BYTE 32).
> While executing: CCL::FD-CHMOD, in process Initial(0).

1 > (:B)

(2AAAAB3B3E68) : 0 (FD-CHMOD -2 438) 78
(2AAAAB3B3EB8) : 1 (OPEN-DUMPLISP-FILE
"/local/fare/lib/exscribe.image" [...]) 701
(2AAAAB3B3F20) : 2 (%SAVE-APPLICATION-INTERNAL
"/local/fare/lib/exscribe.image" [...]) 733

* I wonder if I can now safely transmit arbitrary arguments on the
openmcl command line after -- or so, to be retrieved by
(ccl::command-line-arguments), or if I should still use the hack of
setf'ing cl-launch::*arguments* from a --eval startup argument?

Congratulations for taking openmcl to the x86_64!

[ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.tu=
nes.org ]
Hi! I'm a signature virus. Copy me into your sig file and help me spread!