Re: cl-launch and openmcl
Gary Byers <[email protected]> Fri, 6 Oct 2006 05:37:46 -0600 (MDT)
| Newsgroups | gmane.lisp.openmcl.bugs |
|---|---|
| Message-ID | <[email protected]> |
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-574554015-1160134666=:57104 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 20 Jun 2006, [ISO-8859-1] Far=E9 wrote: Sorry; I didn't even see this message until a moment ago. > 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). I'd guess that it tried to open a file descriptor to "/local/fare/lib/exscr= ibe.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 b= etter if it told you that some component of the pathname didn't exist, and it sho= uld check for this pretty early (before SAVE-APPLICATION has done much of anyth= ing.) > * 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. > Congratulations for taking openmcl to the x86_64! > Thanks for the bug report (and sorry again to have missed it somehow);=20 there will be new snapshots soon. (Any Day Now, as I've been saying for the last 5-6 weeks.) > [ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.= tunes.org ] > Hi! I'm a signature virus. Copy me into your sig file and help me spread! > > _______________________________________________ > Bug-openmcl mailing list > [email protected] > http://clozure.com/mailman/listinfo/bug-openmcl > > --0-574554015-1160134666=: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-574554015-1160134666=:57104--