-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACL regressions on quicklisp collectors #3
Comments
I don't have access to Allegro, I added an ensure finalize call before referencing the class in question. I have no idea if that will resolve the problem as it doesn't seem to cause errors in other lisps. (I have used this to prevent similar issues previously). |
Maybe you know this, but just in case: franz provides free edition of Allegro. |
I wish I could resolve this issues, but running allegro requires me to have either 32bit linux or windows. I notice that acl is no longer in the cl-test-grid results. Is this ticket closable then? |
No one has submitted results, I have no evidence the problem is fixed |
Ok I didnt realise cl-test-grid was a distributed thing, just that allegro results are not included in the current results. Thanks for your response. |
It still fails on ACL. There were ACL submission this month, I will regenerate reports in 10 minutes. Meanwhile, here is a collectors report including history of 5 quicklisp versions: http://common-lisp.net/project/cl-test-grid/tmp/collectors-long-report.html |
I found a mailing list article about this ACL quirk and have hopefully added enough requisite code to make the project build. Thanks for your assistance in this matter |
Hello.
collectors in quicklisp 2014-01-13 fails to build on ACL versions
where it was building OK previously.
The error is "Class #<COMMON-LISP:STANDARD-CLASS ACLMOP:FUNCALLABLE-STANDARD-OBJECT> is not yet finalized."
See test results of collectors on the last two quicklisp versions:
http://common-lisp.net/project/cl-test-grid/library/collectors.html
Clicking the error status in this report opens the build log.
The text was updated successfully, but these errors were encountered: