>>> On Mon, Sep 14, 2015 at 11:15 AM, Faré <fah...@gmail.com> wrote: >>> > On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer <la...@franz.com> wrote: >>> >>>> I suspect any problem Kevin had were related to Allegro somehow having >>> >>>> (user-homedir-pathname) incorrectly returning NIL in their test >>> >>>> configuration. >>> >> >>> >> It's definitely not that: >>> >> >>> >> ;; Current reader case mode: :case-sensitive-lower >>> >> cl-user(1): (user-homedir-pathname) >>> >> #P"C:\\Users\\layer\\" >>> >> cl-user(2): >>> >> >>> > OK. Do you have anything else in your environment that would interfere? >>> > env | grep -i 'appdata|xdg_' >>> > >>> > Can you (trace uiop:xdg-cache-home uiop:xdg-data-home uiop:getenv >>> > uiop:resolve-location uiop:resolve-absolute-location >>> > uiop:resolve-relative-location) in between loading asdf and using it >>> > (with e.g. (asdf:make "asdf")) to narrow down what in >>> > uiop/configuration.lisp is going awry for your cache configuration? >>> > >>> Actually, since the user-cache is computed while asdf is loading, this >>> won't suffice. >>> Can you do the following: >>> >>> (load "build/asdf.lisp") >>> (trace uiop:xdg-cache-home uiop:xdg-data-home uiop:getenv >>> uiop:resolve-location uiop:resolve-absolute-location >>> uiop:resolve-relative-location) >>> (format t "*UC*: ~S~%(CUC): ~S~%" uiop:*user-cache* >>> (uiop/configuration::compute-user-cache)) > > I assume this is moot, given my last email. > No, it's essential — please try it.
As for your previous email, the catch was that the target called "test-scripts" in the minimakefile branch is still confusingly called "test-lisp" in the master branch (I'd fix that, but need to talk to Robert about it). —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The worst thing that can happen to a good cause is, not to be skillfully attacked, but to be ineptly defended. — F. Bastiat
