Faré wrote:
On Mon, Sep 14, 2015 at 11:15 AM, Faré fahree@gmail.com wrote:
On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer layer@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.
This whole branch of that conversation was about an error I got while compiling 3.1.5 asdf.lisp on Windows. I no longer get that error.
So, if you still want me to do the above tracing, what do I do it before?
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).