Re: cl-launch and openmcl

Dear Gary, dear bug-openmcl'ers,

> Sorry; I didn't even see this message until a moment ago.
Thanks for seeing it!

>> * 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).
>
> I'd guess that it tried to open a file descriptor to "/local/fare/lib/exs=
cribe.image"
> got an error return (-2 =3D (- #$ENOENT) =3D "No such file or directory")=
, then tried
> to execute a chmod operation on a bogus file descriptor.  Clearly it'd be=
 better
> if it told you that some component of the pathname didn't exist, and it s=
hould
> check for this pretty early (before SAVE-APPLICATION has done much of any=
thing.)
Must have been that. Dumping an image just worked now that I have this
directory created. Bummer!

>> * 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?
>
> Things after a "--" on the command line aren't parsed by the default lisp
> command line parsing code; anything after a "--" is available in
> CCL:*UNPROCESSED-COMMAND-LINE-ARGUMENTS*.
>
> This was introduced in the 060530 images.
>
This doesn't seem to work when I invoke openmcl with a dumped image:

openmcl test.dump -- a b c
Unrecognized non-option arguments: (test.dump)

Just calling test.dump works.
Is there some magic thing I need to do for the dumped image to be able
to accept arguments, too?

NB: still using the 1.1-pre-060608 (Beta: LinuxX8664) tarball.

[ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.tu=
nes.org ]
Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."  -- Nikodemus Siiv=
ola