Zach Beane xach@xach.com writes:
Faré fahree@gmail.com writes:
It works for me. I suspect you might not have compiled sb-md5 from clean, and due to that bug I fixed in 2.26.9 which required a substantial refactoring, ASDF can now see that file was not up-to-date, when it couldn't see it earlier. Can you recompile this contrib from clean, either in place (by getting proper access rights) or in another directly from which you reinstall afterwards?
What does "compile from clean" mean? What's a way to *not* compile from clean?
FYI, here's a simplified way to reproduce it. From the ASDF source directory, with the latest checkout:
sbcl --non-interactive --no-userinit --load asdf.lisp --eval "(require :sb-md5)"
This lands in the debugger with the permissions error on three different SBCL installations of mine. Am I doing something wrong?
Zach