Re: cl-launch and openmcl

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1596793177-1160169512=:57104
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE



On Fri, 6 Oct 2006, [ISO-8859-1] Far=E9 wrote:

> 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).
>>=20
>> I'd guess that it tried to open a file descriptor to=20
>> "/local/fare/lib/exscribe.image"
>> got an error return (-2 =3D (- #$ENOENT) =3D "No such file or directory"=
), then=20
>> tried
>> to execute a chmod operation on a bogus file descriptor.  Clearly it'd b=
e=20
>> better
>> if it told you that some component of the pathname didn't exist, and it=
=20
>> should
>> check for this pretty early (before SAVE-APPLICATION has done much of=20
>> anything.)
> 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?
>>=20
>> Things after a "--" on the command line aren't parsed by the default lis=
p
>> command line parsing code; anything after a "--" is available in
>> CCL:*UNPROCESSED-COMMAND-LINE-ARGUMENTS*.
>>=20
>> This was introduced in the 060530 images.
>>=20
> 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?
>

The syntax "openmcl <image-name>" is shorthand for "openmcl -I <image-name>=
"
(or "openmcl --image-name <image-name>").  The shorthand only works if
there are no other arguments; if other arguments are present, the -I/--imag=
e-name
qualifiier must be used.  (The "--" handling happens in lisp; the kernel ha=
s
to be able to find the argument that specifies the heap image before anythi=
ng
else. It didn't find such an argument, loaded the default image, and that i=
mage
didn't understand the "naked" test.dump argument.)


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

openmcl --help (or openmcl64 --help) summarizes command-line syntax; it doe=
sn't
mention "--", but probably should.

>
> [ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.=
tunes.org=20
> ]
> Schemer: "Buddha is small, clean, and serious."
> Lispnik: "Buddha is big, has hairy armpits, and laughs."  -- Nikodemus=20
> Siivola
>
>
--0-1596793177-1160169512=:57104
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bug-openmcl mailing list
[email protected]
http://clozure.com/mailman/listinfo/bug-openmcl

--0-1596793177-1160169512=:57104--