On 6/15/11 Jun 15 -9:05 PM, Chun Tian (binghe) wrote:
Hi, Faré
It's caused by LispWorks' ASDF integration feature [1], it's also in attach. I have following line in my LispWorks init file:
(example-compile-file "misc/asdf-integration.lisp" :load t)
I didn't use it much, so I disabled it to make my life easier. But it's also quite hard to determine which version of ASDF2 broke it.
There's nothing obvious in that asdf-integration file that should break asdf's normal functioning. They define a number of behaviors that exploit ASDF data structures, but I don't see anything there that should redefine existing behavior. Of course, I may be overlooking something.
Cheers, r
Hi, Zach
I see current latest Quicklisp release 2011051901 ships with ASDF 2.014.6, but which ASDF version was shipped in last months' Quicklisp? I believe in that ASDF version I didn't met any issue with LispWorks' ASDF integration.
Regards,
Chun Tian (binghe)
[1] http://www.lispworks.com/documentation/lw60/RNIG/html/readme-372.htm#pgfId-9...
在 2011-6-16，02:06， Faré 写道：
My problem still exists after turn to latest ASDF: every time I eval a definition in LispWorks, it warns me that the definition's location changed from a pathname to another same but lower-cased pathname:
Do you know at which version of ASDF, or between which versions of ASDF this behavior started? That would help me track down the relevant change.
Also, what do these return in various versions of ASDF?
(cl:truename "/Users/binghe/Lisp/") (cl:probe-file "/Users/binghe/Lisp/") (asdf::probe-file* "/Users/binghe/Lisp/") (asdf::truenamize "/Users/binghe/Lisp/")
If it's a recent thing, I made a change for LW in 2.016.1. If it's older, I have no idea what it is.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org It is not the employer who pays the wages. Employers only handle the money. It is the customer who pays the wages. — Henry Ford
asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel