[Asdf-devel] ASDF test failure on MKCL linux
test-bundle failed for me, on version 1.1.9 of MKCL: Now for the mono-fasl TEST ABORTED: There is no package with the name MKEXT. 0: (#<compiled-closure 0000000004039500> #<compiled-debug-lexical-info 00007fffcfee80d0>) 1: (#<compiled-function UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX> #<compiled-debug-lexical-info 00007fffcfee82b0>) 2: (#<compiled-function UIOP/IMAGE:PRINT-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8490>) 3: (#<compiled-function UIOP/IMAGE:PRINT-CONDITION-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8660>) 4: (#<bytecompiled-function ASDF-TEST:ACALL> ((ASDF-TEST::ARGS #<a SIMPLE-ERROR 66680128> :COUNT 69 :STREAM #<output strea\ m "stdout">) (ASDF-TEST::NAME . :PRINT-CONDITION-BACKTRACE) (#:|%the-lock--28954-510| . #<lock (recursive) MT:+LOAD-COMPIL\ E-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-511| . T))) 5: (#<bytecompiled-function 00000000035f4f00> (((NIL) (#:G-28954-948 . 0)) (#:G-28954-947) ((NIL) . #:G-28954-946) (ASDF-T\ EST::C . #<a SIMPLE-ERROR 66680128>) (:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecompiled-closure 000000\ 0003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--\ 28954-933| . T))) 6: (#<bytecompiled-function 0000000003628f80> ((ASDF-TEST::NAME . "test-bundle.script") (ASDF-TEST::FILE . ASDF-TEST::|tes\ t-bundle.script|) (#:|%the-lock--28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acqui\ red--28954-983| . T))) 7: (#<compiled-function ASDF/CACHE:CALL-WITH-ASDF-CACHE> #<compiled-debug-lexical-info 00007fffcfeea620>) 8: (#<bytecompiled-function ASDF-TEST::CALL-WITH-TEST> ((:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecomp\ iled-closure 0000000003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (\ #:|%lock-acquired--28954-933| . T))) 9: (#<bytecompiled-function ASDF-TEST:RUN-TEST-SCRIPT> ((ASDF-TEST::FILE . ASDF-TEST::|test-bundle.script|) (#:|%the-lock-\ -28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-983| . T))) 10: (#<bytecompiled-function SI:BYTECODE> NIL) 11: (#<bytecompiled-function SI:BYTECODE> ((SI::OUTPUT-FILE . T) (SI::C-FILE) (SI::H-FILE) (SI::DATA-FILE) (SI::EXTERNAL-F\ ORMAT . :DEFAULT) (SI::VERBOSE . T) (SI::FASL-P . T) (MKCL:QUIT))) 12: (#<bytecompiled-function SI:BYTECODE> NIL) 13: (NIL NIL) Above backtrace due to this condition: There is no package with the name MKEXT. Script failed Using mkcl, test-bundle.script failed Updated mkcl to head from git as of this afternoon, and same error, and this time test-retry-loading-component-1 *also* failed: TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7752937\ 6> Cheers, r Tried updating my mkcl from git and that failed to build on linux: sed '/-CUT-/,$d' ./mkcl/config.h > ./mkcl/config-install.h /bin/bash: ./mkcl/config-install.h: Permission denied make[1]: *** [mkcl/config-install.h] Error 1 make[1]: Leaving directory `/home/rpg/src/mkcl/src' make: *** [all] Error 2
Somehow, what I suspect to be a typo has been introduced in the test-bundle.script in the form of a "MKEXT" package name. MKCL never had a "MKEXT" package but it has a "MK-EXT" package nickname for package "MKCL". The "MK-EXT" nickname is to mimic the "SB-EXT" package in SBCL. So you should either use "MK-EXT" or "MKCL" instead of the faulty package name on line 59 of test-bundle.script. On Sun, Oct 5, 2014 at 5:40 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
test-bundle failed for me, on version 1.1.9 of MKCL:
Now for the mono-fasl
TEST ABORTED: There is no package with the name MKEXT.
0: (#<compiled-closure 0000000004039500> #<compiled-debug-lexical-info 00007fffcfee80d0>) 1: (#<compiled-function UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX> #<compiled-debug-lexical-info 00007fffcfee82b0>) 2: (#<compiled-function UIOP/IMAGE:PRINT-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8490>) 3: (#<compiled-function UIOP/IMAGE:PRINT-CONDITION-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8660>) 4: (#<bytecompiled-function ASDF-TEST:ACALL> ((ASDF-TEST::ARGS #<a SIMPLE-ERROR 66680128> :COUNT 69 :STREAM #<output strea\ m "stdout">) (ASDF-TEST::NAME . :PRINT-CONDITION-BACKTRACE) (#:|%the-lock--28954-510| . #<lock (recursive) MT:+LOAD-COMPIL\ E-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-511| . T)))
5: (#<bytecompiled-function 00000000035f4f00> (((NIL) (#:G-28954-948 . 0)) (#:G-28954-947) ((NIL) . #:G-28954-946) (ASDF-T\ EST::C . #<a SIMPLE-ERROR 66680128>) (:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecompiled-closure 000000\ 0003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--\ 28954-933| . T)))
6: (#<bytecompiled-function 0000000003628f80> ((ASDF-TEST::NAME . "test-bundle.script") (ASDF-TEST::FILE . ASDF-TEST::|tes\ t-bundle.script|) (#:|%the-lock--28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acqui\ red--28954-983| . T)))
7: (#<compiled-function ASDF/CACHE:CALL-WITH-ASDF-CACHE> #<compiled-debug-lexical-info 00007fffcfeea620>) 8: (#<bytecompiled-function ASDF-TEST::CALL-WITH-TEST> ((:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecomp\ iled-closure 0000000003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (\ #:|%lock-acquired--28954-933| . T)))
9: (#<bytecompiled-function ASDF-TEST:RUN-TEST-SCRIPT> ((ASDF-TEST::FILE . ASDF-TEST::|test-bundle.script|) (#:|%the-lock-\ -28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-983| . T))) 10: (#<bytecompiled-function SI:BYTECODE> NIL)
11: (#<bytecompiled-function SI:BYTECODE> ((SI::OUTPUT-FILE . T) (SI::C-FILE) (SI::H-FILE) (SI::DATA-FILE) (SI::EXTERNAL-F\ ORMAT . :DEFAULT) (SI::VERBOSE . T) (SI::FASL-P . T) (MKCL:QUIT)))
12: (#<bytecompiled-function SI:BYTECODE> NIL)
13: (NIL NIL)
Above backtrace due to this condition:
There is no package with the name MKEXT.
Script failed Using mkcl, test-bundle.script failed
Updated mkcl to head from git as of this afternoon, and same error, and this time test-retry-loading-component-1 *also* failed:
TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7752937\ 6>
Cheers, r
Tried updating my mkcl from git and that failed to build on linux: sed '/-CUT-/,$d' ./mkcl/config.h > ./mkcl/config-install.h /bin/bash: ./mkcl/config-install.h: Permission denied make[1]: *** [mkcl/config-install.h] Error 1 make[1]: Leaving directory `/home/rpg/src/mkcl/src' make: *** [all] Error 2
Dear JCB, You suggestion indeed fixes test-bundle.script, but now this test loops indefinitely for me, using the latest mkcl from git: make t l=mkcl t=test-try-refinding.script —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Hardest obstacle / Separating two people, / Misunderstanding On Sun, Oct 5, 2014 at 8:32 PM, Jean-Claude Beaudoin <jean.claude.beaudoin@gmail.com> wrote:
Somehow, what I suspect to be a typo has been introduced in the test-bundle.script in the form of a "MKEXT" package name. MKCL never had a "MKEXT" package but it has a "MK-EXT" package nickname for package "MKCL". The "MK-EXT" nickname is to mimic the "SB-EXT" package in SBCL. So you should either use "MK-EXT" or "MKCL" instead of the faulty package name on line 59 of test-bundle.script.
On Sun, Oct 5, 2014 at 5:40 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
test-bundle failed for me, on version 1.1.9 of MKCL:
Now for the mono-fasl
TEST ABORTED: There is no package with the name MKEXT.
0: (#<compiled-closure 0000000004039500> #<compiled-debug-lexical-info 00007fffcfee80d0>) 1: (#<compiled-function UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX> #<compiled-debug-lexical-info 00007fffcfee82b0>) 2: (#<compiled-function UIOP/IMAGE:PRINT-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8490>) 3: (#<compiled-function UIOP/IMAGE:PRINT-CONDITION-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8660>) 4: (#<bytecompiled-function ASDF-TEST:ACALL> ((ASDF-TEST::ARGS #<a SIMPLE-ERROR 66680128> :COUNT 69 :STREAM #<output strea\ m "stdout">) (ASDF-TEST::NAME . :PRINT-CONDITION-BACKTRACE) (#:|%the-lock--28954-510| . #<lock (recursive) MT:+LOAD-COMPIL\ E-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-511| . T)))
5: (#<bytecompiled-function 00000000035f4f00> (((NIL) (#:G-28954-948 . 0)) (#:G-28954-947) ((NIL) . #:G-28954-946) (ASDF-T\ EST::C . #<a SIMPLE-ERROR 66680128>) (:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecompiled-closure 000000\ 0003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--\ 28954-933| . T)))
6: (#<bytecompiled-function 0000000003628f80> ((ASDF-TEST::NAME . "test-bundle.script") (ASDF-TEST::FILE . ASDF-TEST::|tes\ t-bundle.script|) (#:|%the-lock--28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acqui\ red--28954-983| . T)))
7: (#<compiled-function ASDF/CACHE:CALL-WITH-ASDF-CACHE> #<compiled-debug-lexical-info 00007fffcfeea620>) 8: (#<bytecompiled-function ASDF-TEST::CALL-WITH-TEST> ((:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecomp\ iled-closure 0000000003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (\ #:|%lock-acquired--28954-933| . T)))
9: (#<bytecompiled-function ASDF-TEST:RUN-TEST-SCRIPT> ((ASDF-TEST::FILE . ASDF-TEST::|test-bundle.script|) (#:|%the-lock-\ -28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-983| . T))) 10: (#<bytecompiled-function SI:BYTECODE> NIL)
11: (#<bytecompiled-function SI:BYTECODE> ((SI::OUTPUT-FILE . T) (SI::C-FILE) (SI::H-FILE) (SI::DATA-FILE) (SI::EXTERNAL-F\ ORMAT . :DEFAULT) (SI::VERBOSE . T) (SI::FASL-P . T) (MKCL:QUIT)))
12: (#<bytecompiled-function SI:BYTECODE> NIL)
13: (NIL NIL)
Above backtrace due to this condition:
There is no package with the name MKEXT.
Script failed Using mkcl, test-bundle.script failed
Updated mkcl to head from git as of this afternoon, and same error, and this time test-retry-loading-component-1 *also* failed:
TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7752937\ 6>
Cheers, r
Tried updating my mkcl from git and that failed to build on linux: sed '/-CUT-/,$d' ./mkcl/config.h > ./mkcl/config-install.h /bin/bash: ./mkcl/config-install.h: Permission denied make[1]: *** [mkcl/config-install.h] Error 1 make[1]: Leaving directory `/home/rpg/src/mkcl/src' make: *** [all] Error 2
_______________________________________________ Asdf-devel mailing list Asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On Sun, Oct 5, 2014 at 8:57 PM, Faré <fahree@gmail.com> wrote:
Dear JCB,
You suggestion indeed fixes test-bundle.script, but now this test loops indefinitely for me, using the latest mkcl from git: make t l=mkcl t=test-try-refinding.script
This one does not look like a mere typo. I will have to investigate deeper but I don't have much spare cycles right now so it may take a little while (1-2 days, I hope). I hope this is not blocking something essential, is it? Cheers, Jean-Claude
test-try-refinding.script is a relatively new test (introduced shortly before the 3.1.3 release), so its failure might not be a regression in ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite looping is certainly a bad failure mode in the test. This looks like a MKCL-specific bug, though: If I replace the culprit loop (just before (DBG "Refinding test successful.")) by this debugging variant, I find that the variable tried-once is somehow magically reset to NIL after having been set to T, and that, even if it's a defparameter instead of a lexical variable (I tried both), but happily not with a defvar (where the script only fails, doesn't infinitely loops). The problem is that it restarts the wrong frame! Instead of resuming after the handler-bind handlers from test-try-refinding.script, it resumes a frame way up there in the call stack in function run-test-script in script-support.lisp, that has its own handler-bind (but no restart) via macro with-test. Looks like a MKCL compiler bug. (defvar tried-once nil) (assert ;;(let ((tried-once nil)) (with-asdf-cache (:override t) (handler-bind ((asdf:missing-component #'(lambda (c) (DBG "Caught MISSING-COMPONENT condition.") (nest (progn (DBG 1 tried-once)) (if tried-once (error c)) ;; avoid infinite looping (progn (DBG 2)) (progn (setf tried-once t)) (progn (DBG 3 tried-once)) (let ((missing (asdf::missing-requires c))) (assert (equal missing "test-asdf/force1")) (setf asdf:*central-registry* *old-registry*) (invoke-restart 'asdf:retry)))))) (asdf:find-system "test-asdf/force1" t))));;) Output: Running test-try-refinding.script with mkcl-1.1.10-linux-x64 ;;; Loading "test-try-refinding.script" ; Loading system definition for test-asdf from /home/tunes/cl/asdf/test/test-asdf.asd ;;; Loading "/home/tunes/cl/asdf/test/test-asdf.asd" ; Registering #<SYSTEM "test-asdf"> ; Registering #<SYSTEM "test-asdf/force1"> Clearing the caches and finding. Correctly failed to find system. Caught MISSING-COMPONENT condition. 1 ASDF-TEST::TRIED-ONCE => NIL 2 3 ASDF-TEST::TRIED-ONCE => T Running test-try-refinding.script with mkcl-1.1.10-linux-x64 ;;; Loading "test-try-refinding.script" ... repeat ad vitam aeternam PS: unrelatedly, several bugs were recently fixed in clasp and ECL that may or may not be present in MKCL; check the (not very active, this year) git log of ECL for details. Robert: I suggest we disable this test for MKCL until JCB fixes his compiler bug, and/or use defvar as above. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org As the Chinese say, 1001 words is worth more than a picture. — John McCarthy On Sun, Oct 5, 2014 at 9:20 PM, Jean-Claude Beaudoin <jean.claude.beaudoin@gmail.com> wrote:
On Sun, Oct 5, 2014 at 8:57 PM, Faré <fahree@gmail.com> wrote:
Dear JCB,
You suggestion indeed fixes test-bundle.script, but now this test loops indefinitely for me, using the latest mkcl from git: make t l=mkcl t=test-try-refinding.script
This one does not look like a mere typo. I will have to investigate deeper but I don't have much spare cycles right now so it may take a little while (1-2 days, I hope).
I hope this is not blocking something essential, is it?
Cheers,
Jean-Claude
On Sun, Oct 5, 2014 at 11:03 PM, Faré <fahree@gmail.com> wrote:
test-try-refinding.script is a relatively new test (introduced shortly before the 3.1.3 release), so its failure might not be a regression in ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite looping is certainly a bad failure mode in the test. This looks like a MKCL-specific bug, though:
If I replace the culprit loop (just before (DBG "Refinding test successful.")) by this debugging variant, I find that the variable tried-once is somehow magically reset to NIL after having been set to T, and that, even if it's a defparameter instead of a lexical variable (I tried both), but happily not with a defvar (where the script only fails, doesn't infinitely loops). The problem is that it restarts the wrong frame! Instead of resuming after the handler-bind handlers from test-try-refinding.script, it resumes a frame way up there in the call stack in function run-test-script in script-support.lisp, that has its own handler-bind (but no restart) via macro with-test. Looks like a MKCL compiler bug.
(defvar tried-once nil) (assert ;;(let ((tried-once nil)) (with-asdf-cache (:override t) (handler-bind ((asdf:missing-component #'(lambda (c) (DBG "Caught MISSING-COMPONENT condition.") (nest (progn (DBG 1 tried-once)) (if tried-once (error c)) ;; avoid infinite looping (progn (DBG 2)) (progn (setf tried-once t)) (progn (DBG 3 tried-once)) (let ((missing (asdf::missing-requires c))) (assert (equal missing "test-asdf/force1")) (setf asdf:*central-registry* *old-registry*) (invoke-restart 'asdf:retry)))))) (asdf:find-system "test-asdf/force1" t))));;)
Output: Running test-try-refinding.script with mkcl-1.1.10-linux-x64 ;;; Loading "test-try-refinding.script" ; Loading system definition for test-asdf from /home/tunes/cl/asdf/test/test-asdf.asd ;;; Loading "/home/tunes/cl/asdf/test/test-asdf.asd" ; Registering #<SYSTEM "test-asdf"> ; Registering #<SYSTEM "test-asdf/force1"> Clearing the caches and finding. Correctly failed to find system. Caught MISSING-COMPONENT condition. 1 ASDF-TEST::TRIED-ONCE => NIL 2 3 ASDF-TEST::TRIED-ONCE => T Running test-try-refinding.script with mkcl-1.1.10-linux-x64 ;;; Loading "test-try-refinding.script" ... repeat ad vitam aeternam
Wow! That is bad indeed! I will try to fix it in the coming 24 hours. Thank you for the bug report.
PS: unrelatedly, several bugs were recently fixed in clasp and ECL that may or may not be present in MKCL; check the (not very active, this year) git log of ECL for details.
I do read the ECL git log and bug list on a frequent and regular basis and I try in MKCL each test case mentioned in them when they seem relevant. But the fact is that by now MKCL and ECL have evolved far enough apart that a large (and growing larger) part of those ECL bug reports/fix don't apply to MKCL anymore. I keep on reading though...
Robert: I suggest we disable this test for MKCL until JCB fixes his compiler bug, and/or use defvar as above.
As I said here below, I may take a day or two before I have a fix for this one. So, please, do the workaround in the meantime.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org As the Chinese say, 1001 words is worth more than a picture. — John McCarthy
On Sun, Oct 5, 2014 at 9:20 PM, Jean-Claude Beaudoin <jean.claude.beaudoin@gmail.com> wrote:
On Sun, Oct 5, 2014 at 8:57 PM, Faré <fahree@gmail.com> wrote:
Dear JCB,
You suggestion indeed fixes test-bundle.script, but now this test loops indefinitely for me, using the latest mkcl from git: make t l=mkcl t=test-try-refinding.script
This one does not look like a mere typo. I will have to investigate
deeper
but I don't have much spare cycles right now so it may take a little while (1-2 days, I hope).
I hope this is not blocking something essential, is it?
Cheers,
Jean-Claude
Jean-Claude Beaudoin wrote:
On Sun, Oct 5, 2014 at 11:03 PM, Faré <fahree@gmail.com <mailto:fahree@gmail.com>> wrote:
[...snip...]
If I replace the culprit loop (just before (DBG "Refinding test successful.")) by this debugging variant, I find that the variable tried-once is somehow magically reset to NIL after having been set to T, and that, even if it's a defparameter instead of a lexical variable (I tried both), but happily not with a defvar (where the script only fails, doesn't infinitely loops). The problem is that it restarts the wrong frame! Instead of resuming after the handler-bind handlers from test-try-refinding.script, it resumes a frame way up there in the call stack in function run-test-script in script-support.lisp, that has its own handler-bind (but no restart) via macro with-test. Looks like a MKCL compiler bug.
Wow! That is bad indeed! I will try to fix it in the coming 24 hours. Thank you for the bug report.
[...snip...]
Robert: I suggest we disable this test for MKCL until JCB fixes his compiler bug, and/or use defvar as above.
As I said here below, I may take a day or two before I have a fix for this one. So, please, do the workaround in the meantime.
I don't see the advantage of using the defvar, since it still fails, just without looping forever. So yes, I will disable this test on MKCL for now, and this will not be a blocker for release. [I'm more concerned about the clisp test failures.]
After disabling test-try-refinding, I get two more test failures on MKCL: test-program: ; Registering #<SYSTEM "hello-world-example"> TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7059894\ test-try-recompiling-1: ;;; Loading "/home/rpg/common-lisp/asdf/test/try-reloading-1.asd" Caught error Component "try-reloading-dependency" not found, required by #<SYSTEM "try-reloading-1"> trlc1 5 Running test-retry-loading-component-1.script with mkcl-1.1.10-linux-x64 ;;; Loading "test-retry-loading-component-1.script" Caught error Component "try-reloading-dependency" not found, required by #<SYSTEM "try-reloading-1"> TEST ABORTED: Déjà vu This seems to be another case where the same error is re-encountered. The latter seems like an MKCL bug, perhaps the same bug as test-try-refinding, where the wrong frame gets restarted. The former looks like some disagreement between ASDF and MKCL about what extended MKCL system initialization arguments are permitted. Is it also an MKCL bug, or is it our fault? If it's our fault, so be it. Otherwise, I believe that instead of turning some tests on and off on MKCL (and potentially forgetting to re-enable them), I would rather simply drop MKCL testing until such time as these bugs are fixed. Thoughts? r
On Mon, Oct 6, 2014 at 5:38 PM, Robert Goldman <rpgoldman@sift.net> wrote:
After disabling test-try-refinding, I get two more test failures on MKCL:
test-program:
; Registering #<SYSTEM "hello-world-example"> TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7059894\
Oops, the #+mkcl in hello-world-example.asd was missing a :class program-system — I must never have tested it, and/or must have refactored the code after I did. My bad. Bug in the test, not in asdf. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Be wiser than other people if you can; but do not tell them so. — Chesterfield
Faré wrote:
On Mon, Oct 6, 2014 at 5:38 PM, Robert Goldman <rpgoldman@sift.net> wrote:
After disabling test-try-refinding, I get two more test failures on MKCL:
test-program:
; Registering #<SYSTEM "hello-world-example"> TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7059894\
Oops, the #+mkcl in hello-world-example.asd was missing a :class program-system — I must never have tested it, and/or must have refactored the code after I did. My bad. Bug in the test, not in asdf.
Fails better now. Creates the executable image and uses it successfully, but hangs when trying to use the standalone program. Pushing the fix to the system definition. Cheers, r
On Sun, Oct 5, 2014 at 11:03 PM, Faré <fahree@gmail.com> wrote:
test-try-refinding.script is a relatively new test (introduced shortly before the 3.1.3 release), so its failure might not be a regression in ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite looping is certainly a bad failure mode in the test. This looks like a MKCL-specific bug, though:
It was a bug in MKCL alright! I managed to goof on the order of restarts returned by cl:compute-restarts in a change I did for 1.1.9. A nasty regression you would say. I think it is fixed now (in git repo master head). With this fix I get test-try-refinding.script to run OK and got bold enough to try a run at a 'make t l=mkcl' and it said: -#--------------------------------------- Using /home/jean-claude/CL/MKCL/dev/releases/mkcl-1.1/git/mkcl.git/src/bin/mkcl Ran 55 tests: 55 passing and 0 failing all tests apparently successful -#---------------------------------------
PS: unrelatedly, several bugs were recently fixed in clasp and ECL that may or may not be present in MKCL; check the (not very active, this year) git log of ECL for details.
Arto just posted a few good ones in the last hours, probably the best of the year so far. And I have already merged the relevant ones in MKCL. See, I do watch that stuff...
Jean-Claude Beaudoin wrote:
On Sun, Oct 5, 2014 at 11:03 PM, Faré <fahree@gmail.com <mailto:fahree@gmail.com>> wrote:
test-try-refinding.script is a relatively new test (introduced shortly before the 3.1.3 release), so its failure might not be a regression in ASDF if none of us tested 3.1.3 with MKCL (did we?). Now, infinite looping is certainly a bad failure mode in the test. This looks like a MKCL-specific bug, though:
It was a bug in MKCL alright! I managed to goof on the order of restarts returned by cl:compute-restarts in a change I did for 1.1.9. A nasty regression you would say. I think it is fixed now (in git repo master head).
With this fix I get test-try-refinding.script to run OK and got bold enough to try a run at a 'make t l=mkcl' and it said:
-#--------------------------------------- Using /home/jean-claude/CL/MKCL/dev/releases/mkcl-1.1/git/mkcl.git/src/bin/mkcl Ran 55 tests: 55 passing and 0 failing all tests apparently successful -#---------------------------------------
This morning I pulled an update from the mkcl git repo, rebuilt on my Linux Mint machine, and retested with the latest ASDF. All the tests that completed seemed to complete successfully, but test-program.script hung, instead of completing. Seems to fail in the PROGRAM-OP: test program-op - first, create the standalone program 1> (RUN-PROGRAM ("mkcl" "-norc" "-load" "/home/rpg/common-lisp/asdf/test/make-hello-world.lisp" "-eval" "(asdf-test::make-hello-PROGRAM)") :INPUT NIL :IGNORE-ERROR-STATUS T :OUTP\ UT (#<output stream "stdout"> \ :LINEWISE \ T \ :PREFIX \ "stdout: ") :ERROR-OUTPUT (#<output stream "stdout"> \ :LINEWISE \ T \ :PREFIX \ "stderr: ")) stdout: ;;; Loading "/home/rpg/common-lisp/asdf/test/make-hello-world.lisp" stdout: ;;; Loading "/home/rpg/common-lisp/asdf/build/fasls/mkcl/asdf.fas" stdout: Configuring ASDF stdout: Enabling debugging stdout: Being a bit verbose stdout: Comparing directories stdout: ASDF-TEST:*TEST-DIRECTORY* and stdout: (:PATHNAME-DIRECTORY-PATHNAME (NTH-VALUE 2 (:LOCATE-SYSTEM :TEST-ASDF))) both evaluate to \ same path: stdout: #P"/home/rpg/common-lisp/asdf/test/" stdout: Frob packages stdout: This is make-hello-world, testing its standard-output. stdout: This is make-hello-world, testing its error-output. stdout: This is make-hello-world, testing its stdout. stdout: This is make-hello-world, testing its stderr. stdout: ;;; Loading "/home/rpg/common-lisp/asdf/test/hello-world-example.asd" stdout: ;;; Loading "/home/rpg/common-lisp/asdf/uiop/uiop.asd" stdout: ;;; Loading "/home/rpg/common-lisp/asdf/build/fasls/mkcl-1.1.10-linux-x64/asdf/uiop/uiop.fa\ sb" stdout: ;;; Loading "/home/rpg/common-lisp/asdf/build/fasls/mkcl-1.1.10-linux-x64/asdf/test/hello-w\ orld-example.fasb" stdout: stdout: This is ManKai Common Lisp 1.1.10 stdout: stdout: Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya stdout: Copyright (C) 1993 Giuseppe Attardi stdout: Copyright (C) 2000 Juan J. Garcia-Ripoll stdout: Copyright (C) 2010-2014 Jean-Claude Beaudoin stdout: stdout: ManKai Common Lisp (MKCL) is free software, stdout: and you are welcome to redistribute and/or stdout: modify it under the terms of the GNU LGPL. stdout: See file 'Copyright' in the source code for details. stdout: stdout: Type :h for Help. stdout: Top level in: #<thread "Initial" active (12762) 0x2b388c6abb00 1d34000>. stdout: > <1 (RUN-PROGRAM NIL NIL 0) - use that 1> (RUN-PROGRAM ("/home/rpg/common-lisp/asdf/build/fasls/mkcl-1.1.10-linux-x64/asdf/test/hello-worl\ d-example") :OUTPUT :LINES :ERROR-OUTPUT T) The block of the test that fails is "test program-op", "test image-op" seems to complete successfully. This seems odd to me, since the result of the image test is a standalone program: it doesn't need to be loaded into mkcl: $ ../build/fasls/mkcl-1.1.10-linux-x64/asdf/test/hello-world-exa\ mple--all-systems.image -norc -eval "(uiop:restore-image :entry-point 'hello:entry-point :lisp-inte\ raction nil)" -- a b c d hello, world You passed 4 arguments: "a" "b" "c" "d" So seems like the program-op should be able to do exactly what the image-op does, and work correctly. thanks, r
On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
This morning I pulled an update from the mkcl git repo, rebuilt on my Linux Mint machine, and retested with the latest ASDF. All the tests that completed seemed to complete successfully, but test-program.script hung, instead of completing.
...
The block of the test that fails is "test program-op", "test image-op" seems to complete successfully.
This seems odd to me, since the result of the image test is a standalone program: it doesn't need to be loaded into mkcl:
...
So seems like the program-op should be able to do exactly what the image-op does, and work correctly.
I just tried to have as clean a run at it as I can reasonably have it. So, from a freshly created directory, I did: git clone git://common-lisp.net/projects/mkcl/mkcl.git then built it with: (cd mkcl; configure; cd src; make install-local) then pointed environment variable MKCL to $(pwd)/mkcl/src/bin/mkcl. Followed by: git clone git://common-lisp.net/projects/asdf/asdf.git cd asdf; make t l=mkcl This resulted in: -#--------------------------------------- Using /home/jean-claude/tmp/ASDF/mkcl/src/bin/mkcl Ran 56 tests: 55 passing and 1 failing failing test(s): test-undeferred-warnings.script -#--------------------------------------- To view full results and failures, try the following command: less -p ABORTED build/results/mkcl-test.text make: *** [test-lisp] Error 1 jean-claude@mars> The last line just here above is my normal prompt, so no hang. As you see I do not reproduce the problem you mentioned. BTW, what happens in test-undeferred-warnings seems to be a syntax issue but I am still unclear about it. Cheers, J-C P.S.: all this above is on Ubuntu 12.04 x86_64 with all latest Ubuntu patches.
On Mon, Nov 3, 2014 at 8:30 PM, Jean-Claude Beaudoin <jean.claude.beaudoin@gmail.com> wrote:
cd asdf; make t l=mkcl
This resulted in:
-#--------------------------------------- Using /home/jean-claude/tmp/ASDF/mkcl/src/bin/mkcl Ran 56 tests: 55 passing and 1 failing failing test(s): test-undeferred-warnings.script -#---------------------------------------
I pushed a change to this test script that makes it more portable, by only enabling it on a few supported platforms, which excludes mkcl. I also pushed trivial changes to the manual. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org — Question authority! — Yeah, says who?
Jean-Claude Beaudoin wrote:
On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman <rpgoldman@sift.info <mailto:rpgoldman@sift.info>> wrote:
This morning I pulled an update from the mkcl git repo, rebuilt on my Linux Mint machine, and retested with the latest ASDF. All the tests that completed seemed to complete successfully, but test-program.script hung, instead of completing.
...
The block of the test that fails is "test program-op", "test image-op" seems to complete successfully.
This seems odd to me, since the result of the image test is a standalone program: it doesn't need to be loaded into mkcl:
...
So seems like the program-op should be able to do exactly what the image-op does, and work correctly.
I just tried to have as clean a run at it as I can reasonably have it. So, from a freshly created directory, I did:
git clone git://common-lisp.net/projects/mkcl/mkcl.git <http://common-lisp.net/projects/mkcl/mkcl.git>
then built it with: (cd mkcl; configure; cd src; make install-local)
Hm. I did a slightly different set of steps: cd mkcl ./configure make sudo make install but these look like they should be equivalent (since I didn't set MKCL).
Followed by:
git clone git://common-lisp.net/projects/asdf/asdf.git <http://common-lisp.net/projects/asdf/asdf.git>
cd asdf; make t l=mkcl
This resulted in:
-#--------------------------------------- Using /home/jean-claude/tmp/ASDF/mkcl/src/bin/mkcl Ran 56 tests: 55 passing and 1 failing failing test(s): test-undeferred-warnings.script -#---------------------------------------
To view full results and failures, try the following command: less -p ABORTED build/results/mkcl-test.text make: *** [test-lisp] Error 1 jean-claude@mars>
The last line just here above is my normal prompt, so no hang. As you see I do not reproduce the problem you mentioned.
BTW, what happens in test-undeferred-warnings seems to be a syntax issue but I am still unclear about it.
What happens here is that there is a function with undeclared local variables, but ASDF is not getting a warning from COMPILE-FILE, so it mistakenly believes the build is successful. I don't think I wrote this test properly, though. In a message crossing with this one, Faré has limited its applicability, but I'm not sure I understand the change. Surely that system should not build successfully? Cheers, r
On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
Jean-Claude Beaudoin wrote:
On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman <rpgoldman@sift.info <mailto:rpgoldman@sift.info>> wrote:
This morning I pulled an update from the mkcl git repo, rebuilt on my Linux Mint machine, and retested with the latest ASDF. All the tests that completed seemed to complete successfully, but
test-program.script
hung, instead of completing.
...
The block of the test that fails is "test program-op", "test
image-op"
seems to complete successfully.
This seems odd to me, since the result of the image test is a
standalone
program: it doesn't need to be loaded into mkcl:
...
So seems like the program-op should be able to do exactly what the image-op does, and work correctly.
I just tried to have as clean a run at it as I can reasonably have it. So, from a freshly created directory, I did:
git clone git://common-lisp.net/projects/mkcl/mkcl.git <http://common-lisp.net/projects/mkcl/mkcl.git>
then built it with: (cd mkcl; configure; cd src; make install-local)
Hm. I did a slightly different set of steps:
cd mkcl ./configure make sudo make install
but these look like they should be equivalent (since I didn't set MKCL).
It should be OK, it is just less self-contained in its effects.
Followed by:
git clone git://common-lisp.net/projects/asdf/asdf.git
cd asdf; make t l=mkcl
This resulted in:
-#--------------------------------------- Using /home/jean-claude/tmp/ASDF/mkcl/src/bin/mkcl Ran 56 tests: 55 passing and 1 failing failing test(s): test-undeferred-warnings.script -#---------------------------------------
To view full results and failures, try the following command: less -p ABORTED build/results/mkcl-test.text make: *** [test-lisp] Error 1 jean-claude@mars>
The last line just here above is my normal prompt, so no hang. As you see I do not reproduce the problem you mentioned.
BTW, what happens in test-undeferred-warnings seems to be a syntax issue but I am still unclear about it.
What happens here is that there is a function with undeclared local variables, but ASDF is not getting a warning from COMPILE-FILE, so it mistakenly believes the build is successful.
I don't think I wrote this test properly, though. In a message crossing with this one, Faré has limited its applicability, but I'm not sure I understand the change. Surely that system should not build successfully?
I did a minor modification to test-undeferred-warnings.script and it passes now. Here is what "git diff" says: diff --git a/test/test-undeferred-warnings.script b/test/test-undeferred-warnings.script index 810bcd2..bf1cfdb 100644 --- a/test/test-undeferred-warnings.script +++ b/test/test-undeferred-warnings.script @@ -10,12 +10,12 @@ (def-test-system :undefined-variables :components ((:file "fun-with-undefined-locals"))) -(errors #+(or allegro clozure) compile-file-error +(errors #+(or allegro clozure mkcl) compile-file-error #+(or cmu scl) null #+sbcl compile-failed-error (let ((*compile-file-warnings-behaviour* :error)) (load-system :undefined-variables))) -(errors #+(or allegro clozure) compile-file-error +(errors #+(or allegro clozure mkcl) compile-file-error #+(or cmu scl) null #+sbcl compile-failed-error (let ((*compile-file-warnings-behaviour* :warning)) Maybe a #-(or <all-of-the-above>) should be added after the set of #+ to make sure that macro "errors" always gets the right number of arguments. Cheers, JCB
On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
What happens here is that there is a function with undeclared local variables, but ASDF is not getting a warning from COMPILE-FILE, so it mistakenly believes the build is successful.
I don't think I wrote this test properly, though. In a message crossing with this one, Faré has limited its applicability, but I'm not sure I understand the change. Surely that system should not build successfully?
At least GCL doesn't issue a proper warning in case of undeclared free variable. SBCL, CMUCL and presumably SCL (I believe erroneously) defer such warning until the end of the compilation unit, which when you don't use ASDF's deferred-warnings mechanism, gets caught by the (IMHO bogus) with-compilation-unit (now in a perform-plan method, previously in operate), and thus issue a full warning that isn't checked, and the system thus builds "successfully". I wanted to get rid of that W-C-U, but that broke many systems in Quicklisp that had such bugs. I updated the test (with untested expectations for XCL and SCL, that I can't test anymore). —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org He who says he will die for a cause will probably lie for it and may kill for it. — John McCarthy
On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
Jean-Claude Beaudoin wrote:
On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman <rpgoldman@sift.info <mailto:rpgoldman@sift.info>> wrote:
This morning I pulled an update from the mkcl git repo, rebuilt on my Linux Mint machine, and retested with the latest ASDF. All the tests that completed seemed to complete successfully, but
test-program.script
hung, instead of completing.
The bug in MKCL that resulted in test-program.script hanging is now fixed and committed to MKCL's git repository master head. The fix further uncovered that a change in hello-world-example.asd is now needed for it to work again, please see here-by attached patch file. With this I now get for "make t l=mkcl": -#--------------------------------------- Using /home/jean-claude/tmp/ASDF/mkcl/src/bin/mkcl Ran 56 tests: 56 passing and 0 failing all tests apparently successful -#--------------------------------------- Regards, JCB
Jean-Claude Beaudoin wrote:
On Mon, Nov 3, 2014 at 11:31 PM, Robert P. Goldman <rpgoldman@sift.info <mailto:rpgoldman@sift.info>> wrote:
Jean-Claude Beaudoin wrote: > > On Mon, Nov 3, 2014 at 4:16 PM, Robert P. Goldman <rpgoldman@sift.info <mailto:rpgoldman@sift.info> > <mailto:rpgoldman@sift.info <mailto:rpgoldman@sift.info>>> wrote: > > > This morning I pulled an update from the mkcl git repo, rebuilt on my > Linux Mint machine, and retested with the latest ASDF. All the tests > that completed seemed to complete successfully, but test-program.script > hung, instead of completing. >
The bug in MKCL that resulted in test-program.script hanging is now fixed and committed to MKCL's git repository master head.
The fix further uncovered that a change in hello-world-example.asd is now needed for it to work again, please see here-by attached patch file.
Thanks! I'll get this tested and pushed. I should be able to do that today. Best, Robert
I have pushed JCB's package name fix, and also pushed a fix to the location of the lisp-invocation library for test-program. I still get intermittent failures with test-program that seem to involve some uncontrolled state (in the file system, presumably). I am continuing to look into this. cheers, r Faré wrote:
Dear JCB,
You suggestion indeed fixes test-bundle.script, but now this test loops indefinitely for me, using the latest mkcl from git: make t l=mkcl t=test-try-refinding.script
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Hardest obstacle / Separating two people, / Misunderstanding
On Sun, Oct 5, 2014 at 8:32 PM, Jean-Claude Beaudoin <jean.claude.beaudoin@gmail.com> wrote:
Somehow, what I suspect to be a typo has been introduced in the test-bundle.script in the form of a "MKEXT" package name. MKCL never had a "MKEXT" package but it has a "MK-EXT" package nickname for package "MKCL". The "MK-EXT" nickname is to mimic the "SB-EXT" package in SBCL. So you should either use "MK-EXT" or "MKCL" instead of the faulty package name on line 59 of test-bundle.script.
On Sun, Oct 5, 2014 at 5:40 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
test-bundle failed for me, on version 1.1.9 of MKCL:
Now for the mono-fasl
TEST ABORTED: There is no package with the name MKEXT.
0: (#<compiled-closure 0000000004039500> #<compiled-debug-lexical-info 00007fffcfee80d0>) 1: (#<compiled-function UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX> #<compiled-debug-lexical-info 00007fffcfee82b0>) 2: (#<compiled-function UIOP/IMAGE:PRINT-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8490>) 3: (#<compiled-function UIOP/IMAGE:PRINT-CONDITION-BACKTRACE> #<compiled-debug-lexical-info 00007fffcfee8660>) 4: (#<bytecompiled-function ASDF-TEST:ACALL> ((ASDF-TEST::ARGS #<a SIMPLE-ERROR 66680128> :COUNT 69 :STREAM #<output strea\ m "stdout">) (ASDF-TEST::NAME . :PRINT-CONDITION-BACKTRACE) (#:|%the-lock--28954-510| . #<lock (recursive) MT:+LOAD-COMPIL\ E-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-511| . T)))
5: (#<bytecompiled-function 00000000035f4f00> (((NIL) (#:G-28954-948 . 0)) (#:G-28954-947) ((NIL) . #:G-28954-946) (ASDF-T\ EST::C . #<a SIMPLE-ERROR 66680128>) (:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecompiled-closure 000000\ 0003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--\ 28954-933| . T)))
6: (#<bytecompiled-function 0000000003628f80> ((ASDF-TEST::NAME . "test-bundle.script") (ASDF-TEST::FILE . ASDF-TEST::|tes\ t-bundle.script|) (#:|%the-lock--28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acqui\ red--28954-983| . T)))
7: (#<compiled-function ASDF/CACHE:CALL-WITH-ASDF-CACHE> #<compiled-debug-lexical-info 00007fffcfeea620>) 8: (#<bytecompiled-function ASDF-TEST::CALL-WITH-TEST> ((:ASDF-TEST-DONE . :ASDF-TEST-DONE) (ASDF-TEST::THUNK . #<bytecomp\ iled-closure 0000000003d48180>) (#:|%the-lock--28954-932| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (\ #:|%lock-acquired--28954-933| . T)))
9: (#<bytecompiled-function ASDF-TEST:RUN-TEST-SCRIPT> ((ASDF-TEST::FILE . ASDF-TEST::|test-bundle.script|) (#:|%the-lock-\ -28954-982| . #<lock (recursive) MT:+LOAD-COMPILE-LOCK+ 00000000010b5280>) (#:|%lock-acquired--28954-983| . T))) 10: (#<bytecompiled-function SI:BYTECODE> NIL)
11: (#<bytecompiled-function SI:BYTECODE> ((SI::OUTPUT-FILE . T) (SI::C-FILE) (SI::H-FILE) (SI::DATA-FILE) (SI::EXTERNAL-F\ ORMAT . :DEFAULT) (SI::VERBOSE . T) (SI::FASL-P . T) (MKCL:QUIT)))
12: (#<bytecompiled-function SI:BYTECODE> NIL)
13: (NIL NIL)
Above backtrace due to this condition:
There is no package with the name MKEXT.
Script failed Using mkcl, test-bundle.script failed
Updated mkcl to head from git as of this afternoon, and same error, and this time test-retry-loading-component-1 *also* failed:
TEST ABORTED: Error while trying to load definition for system hello-world-example from pathname /home/rpg/common-lisp/asd\ f/test/hello-world-example.asd: Unknown initialization option :EPILOGUE-CODE for class #<The STANDARD-CLASS SYSTEM 7752937\ 6>
Cheers, r
Tried updating my mkcl from git and that failed to build on linux: sed '/-CUT-/,$d' ./mkcl/config.h > ./mkcl/config-install.h /bin/bash: ./mkcl/config-install.h: Permission denied make[1]: *** [mkcl/config-install.h] Error 1 make[1]: Leaving directory `/home/rpg/src/mkcl/src' make: *** [all] Error 2
_______________________________________________ Asdf-devel mailing list Asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
participants (4)
-
Faré -
Jean-Claude Beaudoin -
Robert Goldman -
Robert P. Goldman