ASDF no longer builds on ACL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ASDF |
Fix Released
|
Critical
|
Robert P. Goldman |
Bug Description
Tested on Mac OS X. Interestingly, the problem is not that ASDF itself doesn't build cleanly: the error is that the ASDF *tools* don't build cleanly. Probably this should not be breaking the ASDF build. I have not had time to check this, but I would guess from the error messages that there are bugs in macro-generated code, because the code the warnings are about looks like something that no human would write.
Here's the transcript:
rpg@rpgoldman-2: ~/lisp/asdf $ make test l=allegro_64
./make.sh l='allegro_64' L='' u='' U='' v='' s='' t='' test
;Compiler warnings for "home:lisp;
; In BUILD-ASDF: Suspicious lambda-list: (&OPTIONAL)
; In DOC: Suspicious lambda-list: (&OPTIONAL)
; In WEBSITE: Suspicious lambda-list: (&OPTIONAL)
; In WC: Suspicious lambda-list: (&OPTIONAL)
; In LIST-SOURCE-
; Warning: Lisp compilation had style-warnings while compiling #<CL-SOURCE-FILE "asdf-tools" "build">
; While executing: CHECK-LISP-
;Compiler warnings for "home:lisp;
; In CLEAN: Suspicious lambda-list: (&OPTIONAL)
; In %PUSH: Suspicious lambda-list: (&OPTIONAL)
; In MERGE-MASTER-
; In FIX-LOCAL-GIT-TAGS: Suspicious lambda-list: (&OPTIONAL)
; In GIT-ALL-
; In EXT-INIT: Suspicious lambda-list: (&OPTIONAL)
; In EXT-CLEAR: Suspicious lambda-list: (&OPTIONAL)
; In EXT-RESET: Suspicious lambda-list: (&OPTIONAL)
; In EXT-UPDATE: Suspicious lambda-list: (&OPTIONAL)
; Warning: Lisp compilation had style-warnings while compiling #<CL-SOURCE-FILE "asdf-tools" "git">
; While executing: CHECK-LISP-
;Compiler warnings for "home:lisp;
; In TEST-ASCII: Suspicious lambda-list: (&OPTIONAL)
; Warning: Lisp compilation had style-warnings while compiling #<CL-SOURCE-FILE "asdf-tools" "test-basic">
; While executing: CHECK-LISP-
;Compiler warnings for "home:lisp;
; In TEST-ALL-
; In TEST-ALL: Suspicious lambda-list: (&OPTIONAL)
; In TEST-ALL-
; In TEST-ALL-NO-STOP: Suspicious lambda-list: (&OPTIONAL)
; In CHECK-ALL-
; In CHECK-ALL-
; In CHECK-ALL-RESULTS: Suspicious lambda-list: (&OPTIONAL)
; Warning: Lisp compilation had style-warnings while compiling #<CL-SOURCE-FILE "asdf-tools" "test-all">
; While executing: CHECK-LISP-
;Compiler warnings for "home:lisp;
; In MAKE-UIOP-TARBALL: Suspicious lambda-list: (&OPTIONAL)
; In MAKE-ASDF-
; In MAKE-ASDF-
; In MAKE-ASDF-LISP: Suspicious lambda-list: (&OPTIONAL)
; In MAKE-ARCHIVE: Suspicious lambda-list: (&OPTIONAL)
; In PUBLISH-ARCHIVE: Suspicious lambda-list: (&OPTIONAL)
; In LINK-ARCHIVE: Suspicious lambda-list: (&OPTIONAL)
; In MAKE-AND-
; Warning: Lisp compilation had style-warnings while compiling #<CL-SOURCE-FILE "asdf-tools" "release">
; While executing: CHECK-LISP-
makeinfo --html asdf.texinfo \
2>&1 > manual-html.log || { echo "failed. See log in manual-html.log" ; exit 1 ;}
Now starting allegro_64, loading the script support, and exiting without doing anything...
/usr/local/
SUCCEEDED at starting allegro_64, loading the script support, and exiting without doing anything.
Now starting allegro_64, loading the script support, loading ASDF from source, then exiting...
/usr/local/
FAILED at starting allegro_64, loading the script support, loading ASDF from source, then exiting.
Changed in asdf: | |
milestone: | asdf3.2 → 3.1.7 |
status: | Fix Committed → Fix Released |
What is the value of the LISP variable? If not set, it defaults to CCL.
I see that indeed CCL seems to issue this warning:
? (defun foo (&optional) 1)
;Compiler warnings :
; In FOO: Suspicious lambda-list: (&OPTIONAL)
Somehow, it doesn't show any warning I use asdf-tools, even if I rm -rf build/fasls/
... and the reason is that I have quicklisp in my home directory, at which point asdf-tools compiled with ql:quickload, which seems to suppress this warning (!)
When I rm -rf build/fasls/ and mv ~/quickload ~/quickload.bak, I do get the same error that you do.
That's weird, because it's a style warning, anyway, so shouldn't break the build.
I can workaround this by suppressing style-warning's :around-compile asdf-tools, but this suggests a deeper problem with compiler warning detection.