On Oct 22, 2013, at 20:26, Faré fahree@gmail.com wrote:
Testing ASDF found several bugs in ABCL.
cd ~/cl/asdf/
abcl --noinform --eval '(or`#.(load(string`|test/script-support.lisp|)`:verbose():print())#.(asdf-test::exit-lisp`0))' Failed to require LOOP because 'Illegal function object: (bqv).'
Maximum error depth exceeded (11 nested errors) with 'Illegal function object: (bqv).'.
abcl --noinform --eval "(or'#.(load(string'|test/script-support.lisp|):verbose():print())#.(asdf-test::exit-lisp'0))"
So your backquote parser is broken somehow.
I have confirmed this bug on my end.
I would file a ticket for this, but we are in the process of moving abcl.org to another machine with better connectivity, so am trying to get that finished (famous last words: “next day or two”) before updating state that will need to be resynced.
Also, upgrading from ASDF 2.25 or 2.26 used to work, but not anymore. Now 2.27 is needed (as configured in header.lisp, and tested with make u l=abcl ASDF_UPGRADE_TEST_TAGS=2.25).
Hmm.
make u l=abcl ASDF_UPGRADE_TEST_TAGS=2.25
works for me with an ASDF at git version
commit 10fa87ab70d7db14b45ad822558382fe3dad4540 Author: Francois-Rene Rideau tunes@google.com Date: Tue Oct 22 23:43:42 2013 -0400
Debian release for 3.0.3 (Also, slight update to web page.)
on ABCL of
"1.3.0-dev" "Java_HotSpot(TM)_64-Bit_Server_VM-Oracle_Corporation-1.7.0_45-b18" "x86_64-Mac_OS_X-10.9”
How can we narrow the possibilities for why it works for me, but not for you?
Finally, there are many instances of abcl in #+ or #- in the test/ directory, including two new ones in test-bundle on Mac (which is a regression from abcl 1.1.0) and in test-stamp-propagation (which is a new test, and a bug shared with XCL).
That’s an implicit invitation for help quashing bugs, right? Probably I do not have the cycles to help for your impending release, but will throw it on my TODO stack.
--
"A screaming comes across the sky. It has happened before but there is nothing to compare to it now."