[asdf-devel] clisp 2.49 still fails tests ...
On Mac OS X I get: BAD: Loading ASDF on clisp produces messages make[1]: *** [test-clean-load] Error 1 make: *** [test-all-noupgrade] Error 1 But I think it passes all the actual tests: -#--- Using clisp Ran 44 tests: 44 passing and 0 failing all tests apparently successful -#--- Maybe makefile testing needs to be modified to ignore these messages for clisp? IIRC you were saying they were not avoidable... best, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
[asdf-devel] More test failures on Mac OSX
1. ecl ECL (Embeddable Common-Lisp) 12.12.1 -#--- Using ecl Ran 44 tests: 42 passing and 2 failing failing test(s): test-multiple.script test-run-program.script -#--- 2. abcl Armed Bear Common Lisp 1.1.0.2 -#--- Using abcl Ran 44 tests: 42 passing and 2 failing failing test(s): test-encodings.script test-logical-pathname.script -#--- I ran ccl clisp sbcl ecl abcl allegro allegromodern For allegro, I tested both 8.2 and 9.0. So this is pretty darn good! Best, Robert ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] clisp 2.49 still fails tests ...
On 2/4/13 Feb 4 -5:58 PM, Faré wrote: On Mon, Feb 4, 2013 at 5:02 PM, Robert Goldman rpgold...@sift.info wrote: On Mac OS X I get: BAD: Loading ASDF on clisp produces messages make[1]: *** [test-clean-load] Error 1 make: *** [test-all-noupgrade] Error 1 But I think it passes all the actual tests: Maybe makefile testing needs to be modified to ignore these messages for clisp? IIRC you were saying they were not avoidable... I fixed the test scripts to be more robust so CLISP is doesn't fail this way. Works like a charm, thanks. Just tested and clisp is now happy. Best, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
[asdf-devel] can't run quicklisp with asdf 2.28 on CCL (upgrage issue?)
I placed new asdf.lisp into quicklisp and changed (defvar *required-asdf-version* 2.28) in quicklisp/setup.lisp to the lates version - 2.28. lisps/ccl-1.8/lx86cl --no-init --load quicklisp-patched2/setup.lisp Error: Error while trying to load definition for system quicklisp from pathname /home/testgrid/quicklisp-patched2/quicklisp/quicklisp.asd: Undefined function #:|ASDF::COMPONENT-VERSION| called with arguments (2012112500 #SYSTEM quicklisp) . While executing: (:INTERNAL ASDF/FIND-SYSTEM:LOAD-ASD), in process listener(1). Type :GO to continue, :POP to abort, :R for a list of available restarts. If continued: Retry applying #:|ASDF::COMPONENT-VERSION| to (2012112500 #SYSTEM quicklisp). Type :? for other options. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] can't run quicklisp with asdf 2.28 on CCL (upgrage issue?)
On Tue, Feb 5, 2013 at 4:03 AM, Anton Vodonosov avodono...@yandex.ru wrote: I placed new asdf.lisp into quicklisp and changed (defvar *required-asdf-version* 2.28) in quicklisp/setup.lisp to the lates version - 2.28. This looks like the bad interaction of files compiled with a previous ASDF and files compiled with the new one. Did you clean your fasl cache after you upgraded? I'll investigate tomorrow. It's also possible that my upgrade tricks don't work so well on CCL, and I need to punt like I do on CLISP. However, CCL does pass all my automated upgrade tests so far, so if that's the case I need to improve those tests. —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org Pournelle's Iron Law of Bureaucracy states that in any bureaucratic organization there will be two kinds of people: those who work to further the actual goals of the organization, and those who work for the organization itself. Examples in education would be teachers who work and sacrifice to teach children, vs. union representative who work to protect any teacher including the most incompetent. The Iron Law states that in all cases, the second type of person will always gain control of the organization, and will always write the rules under which the organization functions. lisps/ccl-1.8/lx86cl --no-init --load quicklisp-patched2/setup.lisp Error: Error while trying to load definition for system quicklisp from pathname /home/testgrid/quicklisp-patched2/quicklisp/quicklisp.asd: Undefined function #:|ASDF::COMPONENT-VERSION| called with arguments (2012112500 #SYSTEM quicklisp) . While executing: (:INTERNAL ASDF/FIND-SYSTEM:LOAD-ASD), in process listener(1). Type :GO to continue, :POP to abort, :R for a list of available restarts. If continued: Retry applying #:|ASDF::COMPONENT-VERSION| to (2012112500 #SYSTEM quicklisp). Type :? for other options. ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Re: [asdf-devel] can't run quicklisp with asdf 2.28 on CCL (upgrage issue?)
05.02.2013, 07:44, Faré fah...@gmail.com: On Tue, Feb 5, 2013 at 4:03 AM, Anton Vodonosov avodono...@yandex.ru wrote: I placed new asdf.lisp into quicklisp and changed (defvar *required-asdf-version* 2.28) in quicklisp/setup.lisp to the lates version - 2.28. This looks like the bad interaction of files compiled with a previous ASDF and files compiled with the new one. Did you clean your fasl cache after you upgraded? I'll investigate tomorrow. Yes, I did rm -r .cache/common-lisp/ ___ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
