On 3/22/10 Mar 22 -10:04 PM, Faré wrote:
On 22 March 2010 22:35, Faré fah...@gmail.com wrote:
On 22 March 2010 22:13, Robert Goldman rpgold...@sift.info wrote:
Would it be possible to use the normal rewrite rules in the tests?
Sure but then we should either
1- always recompile asdf.lisp (as
Quick follow-up: I encountered the bug again when testing with 8.2
allegromodern
This suggests there may be 1 bug here. One bug being the fact that
the RESTART throws us into an infinite loop.
That's a bug. I don't know anything about it, though.
It may have already existed, or I may have
I understand about the change to the output, and the not recompiling, but I
think you're not using the standard implementation rewriting rules, because,
e.g., all the modern lisp binaries are going into mlisp, whereas ordinarily
8.1 and 8.2 fasls would go into different directories, right?
On 22 March 2010 22:13, Robert Goldman rpgold...@sift.info wrote:
I understand about the change to the output, and the not recompiling, but I
think you're not using the standard implementation rewriting rules, because,
e.g., all the modern lisp binaries are going into mlisp, whereas
On 22 March 2010 22:35, Faré fah...@gmail.com wrote:
On 22 March 2010 22:13, Robert Goldman rpgold...@sift.info wrote:
Would it be possible to use the normal rewrite rules in the tests?
Sure but then we should either
1- always recompile asdf.lisp (as before)
or
2- copy all the
On 3/21/10 Mar 21 -10:49 AM, Robert Goldman wrote:
Now when I run the tests on allegro I get a FILE-INCOMPATIBLE-FASL-ERROR
on file3.fasl. ASDF then tries to invoke the ASDF:RETRY restart. Then
it gets the FILE-INCOMPATIBLE-FASL-ERROR on file3.fasl. ASDF then tries
to invoke the ASDF:RETRY
