> > 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/ > > Are you sure that sbcl doesn't have copies of those fasls in /usr/local? It's been a while since I've used sbcl on debian..
Another thing to check: do the fasls in ~/.cache get regenerated. If yes, that makes sense, if not, that indicates theres a cached copy elsewhere. > 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. > But not the clbuild packages I hope! > > 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 > So did you clbuild update the packages? And can you check if the clbuild/systems link for weblocks.asd is correct? > 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? > I think that's what's happened. But Leslie reported a few days ago that this error only happens with weblocks-stable. Can you try this? To src/package.lisp add another shadowing-import line like this: (:shadowing-import-from :cl-who #:str) Does that fix the problem? But I thought of checking first here. This is the right place to check! This is the second cl-who:str report in a week. -- 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.
