On Thu, Feb 7, 2013 at 3:36 AM, Anton Vodonosov avodonosov@yandex.ru wrote:
Meantime the SBCL results for ASDF 2.28.4
Diff comparing to 2.28: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-7.html (don't pay attention to weblocks-test, it crushes sometimes when SBCL runs out of heap)
OK, so that's (small) progress.
comparing to not patched quicklisp: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-8.html
What are those compilation failures due to warnings?
ASDF is correctly catching undefined-variable warnings that it wasn't catching before. These warnings were always there, but previously, ASDF1 and 2 was failing to check for them and consequently fail the build, because of its WITH-COMPILATION-UNIT. ASDF 3, which handles WITH-COMPILATION-UNIT correctly on SBCL and CCL, catches these warnings and now fails the build as per SBCL's default *compile-file-warning-behaviour*. This is actually progress.
The authors of all these packages need to fix them.
Now what's the right path to go from here to there, and should we kluge ASDF in the meantime, I'm not sure. Setting asdf:*warnings-file-type* to NIL should restore the previous behavior and catch fewer warnings.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org It's not ignorance that does so much damage; it's knowing so darned much that ain't so. — Josh Billings