Hi;

The following command:

    lx86cl64 --eval '(ql:quickload :weblocks-prototype-js)'

fails thusly:

...

*[package drakma].................................. *
*[package cl-tidy]................................. *
*[package weblocks-utils].................. *
*Read error between positions 5697 and 9088 in 
/home/jm/quicklisp/dists/quicklisp/software/weblocks-utils-2017012*
*4-git/debug-app.lisp. *
*> Error: There is no package named "SB-KERNEL" . *
*> While executing: CCL::%PARSE-TOKEN, in process listener(1). *
*> Type :GO to continue, :POP to abort, :R for a list of available 
restarts. *
*> If continued: Retry finding package with name "SB-KERNEL". *
*> Type :? for other options. *


Environment:

   - Quicklisp: 2018-04-30
   - weblocks-prototype-js-20160929-git
   - Clozure Common Lisp Version 1.11.5/v1.11.5  (LinuxX8664)
   - Linux jm7 4.15.17-200.fc26.x86_64 #1 SMP Thu Apr 12 18:28:26 UTC 2018 
   x86_64 x86_64 x86_64 GNU/Linux
   - fedora-release-26-1.noarch
   

Less briefly: SBCL complains about "probably a bug in SBCL" when I try to 
load my weblocks-based webapp under certain conditions (trying to dump an 
image).  In tracking it down, it seemed reasonable to see if my app worked 
under CCL (like my various other non-weblocks-based CL apps are happy to 
do).  It had been a while since I had run this particular app under CCL, 
and probably before the requirement to specify the particular (prototype) 
backend.

It appears there is a naked implementation-specific call to 
sb-kernel:dynamic-usage to appear in weblocks-utils-20170124-git.

Might I be so bold as to suggest perhaps something like 
https://gist.github.com/chaitanyagupta/671e3880dc24a2763d1653a9c1ea6b0f
 instead?
 
Thanks for the cool software!

-jm

-- 
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/weblocks.
For more options, visit https://groups.google.com/d/optout.

Reply via email to