On Fri, Sep 10, 2010 at 13:52, Nandan Bagchee <[email protected]> wrote: >> >> http://bitbucket.org/S11001001/weblocks-dev >> sbcl: 1.0.42 and 1.0.42.35 (latest dev downloaded today) >> >> I've managed to reproduce the same error in all of the combinations of >> weblocks and sbcl, with or without slime. I don't know if the problem >> is within my configuration setup. I've tried to remove all of the >> fasls in every combination prior to compiling, and to restart the sbcl > > What command did you use to remove the fasls? If your sbcl was installed > using package mgmt (apt-get, for example) the fasls are going to lie in some > /opt or /var dir, iirc. > I am going to see if I can reproduce this today.
I have compiled the sbcl and it is located in the /usr/local, and I have purged all of the ubuntu sbcl packages. As far as I can tell, the default configuration for the sbcl if it is compiled and not downloaded as the deb package is to put the fasls into $HOME/.cache/common-lisp/sbcl-version/appropriate-path-to-compiled-lisp-packages... and those I have removed with simple rm -r $HOME/.cache/common-lisp/ I've tried to locate all of the fasls (as root) with find but at the moment all of the fasls still remaining in my system are located in the /usr/local/lib/sbcl as part of the sbcl packages. About an month ago I've tried the weblocks demo for the first time, and it did work. I was using an version of the sbcl prior the 1.0.42, and latest stable weblocks, so my guess is that either I have misconfigured something, or perhaps the sbcl guys have either created an bug, or made the sbcl more strict about packages in some way. Or, perhaps CL-WHO or PARENSCRIPT teams had made some changes? But I thought of checking first here. -- Poći ću s vama jer volim šalu, hoću da vidim ježa budalu. Put u Japan - http://ofcan.wordpress.com -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
