Re: cl-launch and openmcl

Thanks! It works much better now. I've just released cl-launch 1.89
with improved openmcl support, including image dump and direct
command-line arguments.
   http://www.cliki.net/cl-launch

Testing, however, reveals unstability in openmcl, at least the tarball
I'm using.
   cl-launch -l openmcl -B tests 114 114
goes into the debugger with a
Read error between positions 10 and 7932 in /local/fare/tsts/clt-out.sh
while trying to compile-file clt-out.sh using the 1.1-pre-060608
(Beta: LinuxX8664) tarball.

I'll try with a more recent tarball later. You can try with your own by run=
ning
  cl-launch -l openmcl -B tests
in a fresh directory (it creates junk files).

[ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.tu=
nes.org ]
Most economic fallacies derive... from the tendency to assume that there
is a fixed pie, that one party can gain only at the expense of another.
        -- Milton Friedman


On 06/10/06, Gary Byers <[email protected]> wrote:
>> openmcl test.dump -- a b c
>> Unrecognized non-option arguments: (test.dump)
> The syntax "openmcl <image-name>" is shorthand for "openmcl -I <image-nam=
e>"
> (or "openmcl --image-name <image-name>").  The shorthand only works if
> there are no other arguments; if other arguments are present, the -I/--im=
age-name
> qualifiier must be used.  (The "--" handling happens in lisp; the kernel =
has
> to be able to find the argument that specifies the heap image before anyt=
hing
> else. It didn't find such an argument, loaded the default image, and that=
 image
> didn't understand the "naked" test.dump argument.)