Fare, here are the results for quicklisp 2013-01-28 patched with asdf 2.28 and new version of asdf-system-connections: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-6.html
As you see there are failures. One of the most often errors is "Unhandled SERIOUS-CONDITION of type COMPILE-FAILED-ERROR is signaled: Lisp compilation failed", but there are some other errors.
Best regards, - Anton
Anton Vodonosov avodonosov@yandex.ru writes:
Fare, here are the results for quicklisp 2013-01-28 patched with asdf 2.28 and new version of asdf-system-connections: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-6.html
As you see there are failures. One of the most often errors is "Unhandled SERIOUS-CONDITION of type COMPILE-FAILED-ERROR is signaled: Lisp compilation failed", but there are some other errors.
You might want to try the :verbose t option to quickload to get more detailed progress output.
Zach
06.02.2013, 01:12, "Zach Beane" xach@xach.com:
Anton Vodonosov avodonosov@yandex.ru writes:
Fare, here are the results for quicklisp 2013-01-28 patched with asdf 2.28 and new version of asdf-system-connections: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-6.html
As you see there are failures. One of the most often errors is "Unhandled SERIOUS-CONDITION of type COMPILE-FAILED-ERROR is signaled: Lisp compilation failed", but there are some other errors.
You might want to try the :verbose t option to quickload to get more detailed progress output.
Zach
OK, will do so in the future.
Most of these COMPILE_FAILED_ERROS are caused by WARNINGs:
* (ql:quickload :json-template :verbose t) To load "json-template": Load 1 ASDF system: json-template ; Loading "json-template"
; file: /home/testgrid/quicklisp-patched2/dists/quicklisp/software/cl-json-template-20110418-hg/json-template.lisp ; in: DEFUN JSON-TEMPLATE::EXPAND-THINGS-TO-STREAM ; (ASSOC FORMATTER JSON-TEMPLATE:*TEMPLATE-FORMATTERS* :TEST #'EQUAL) ; ; caught WARNING: ; undefined variable: JSON-TEMPLATE:*TEMPLATE-FORMATTERS* ; ; compilation unit finished ; Undefined variable: ; JSON-TEMPLATE:*TEMPLATE-FORMATTERS* ; caught 1 WARNING condition
debugger invoked on a ASDF/LISP-BUILD:COMPILE-FAILED-ERROR in thread #<THREAD "main thread" RUNNING {AB1FD19}>: Lisp compilation failed
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry completing compilation for #<SYSTEM "json-template">. 1: [ACCEPT] Continue, treating completing compilation for #<SYSTEM "json-template"> as having been successful. 2: [ABORT ] Give up on "json-template" 3: Exit debugger, returning to top level.
(ASDF/LISP-BUILD:CHECK-LISP-COMPILE-WARNINGS T T NIL NIL)
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)
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?
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