[armedbear-devel] strange asdf behavior with 0.20.0
I just installed 0.20.0 and am now unable to load usocket, yet I can still load cl-ppcre and other Edi-ware. Upon rolling back to 0.19.1, the same usocket package compiles and loads just fine. I have tried using the binary distribution of 0.20.0 as well as building my own, with the same result. There does not seem to be anything wrong with the usocket package definition itself. Has anyone else seen this or know what is going on? Here is the output of 0.20.0: raison@mercury:~/.abcl/lib$ abcl Armed Bear Common Lisp 0.20.0 Java 1.6.0_20 Sun Microsystems Inc. Java HotSpot(TM) Server VM Low-level initialization completed in 0.614 seconds. Startup completed in 1.739 seconds. Type ":help" for a list of available commands. CL-USER(1): (asdf:oos 'asdf:load-op 'usocket) ; loading system definition from /home/raison/.abcl/systems/usocket.asd into #<PACKAGE "ASDF0"> Error loading /home/raison/.abcl/site/usocket-svn/usocket.asd at line 38 (offset 1255) #<THREAD "interpreter" {373E38}>: Debugger invoked on condition of type LOAD-SYSTEM-DEFINITION-ERROR Error while trying to load definition for system usocket from pathname /home/raison/.abcl/systems/usocket.asd: Unrecognized keyword argument :NAME Restarts: 0: TOP-LEVEL Return to top level. [1] USOCKET-SYSTEM(2): -Kevin
On 6/9/10 8:20 PM, Kevin Raison wrote:
I just installed 0.20.0 and am now unable to load usocket, yet I can still load cl-ppcre and other Edi-ware. Upon rolling back to 0.19.1, the same usocket package compiles and loads just fine. I have tried using the binary distribution of 0.20.0 as well as building my own, with the same result. There does not seem to be anything wrong with the usocket package definition itself. Has anyone else seen this or know what is going on? Here is the output of 0.20.0:
[…] Seemingly a bug in ABCL macro expansion for keyword arguments for which a value is NIL with additional arguments in the list. For now, if you aren't using SBCL with the same usocket.asd you can patch usocket with the attached patch. Thanks for the report. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On Jun 10, 2010, at 7:13 AM, Mark Evenson wrote:
On 6/9/10 8:20 PM, Kevin Raison wrote:
I just installed 0.20.0 and am now unable to load usocket, yet I can still load cl-ppcre and other Edi-ware. Upon rolling back to 0.19.1, the same usocket package compiles and loads just fine. I have tried using the binary distribution of 0.20.0 as well as building my own, with the same result. There does not seem to be anything wrong with the usocket package definition itself. Has anyone else seen this or know what is going on? Here is the output of 0.20.0:
[…]
Seemingly a bug in ABCL macro expansion for keyword arguments for which a value is NIL with additional arguments in the list.
The [offending changeset was r12693][1], that being Erik's fix for dispatch macro in Stream.java which returns NIL values. [1]: http://trac.common-lisp.net/armedbear/changeset/12693 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 6/10/10 7:13 AM, Mark Evenson wrote:
On 6/9/10 8:20 PM, Kevin Raison wrote:
I just installed 0.20.0 and am now unable to load usocket, yet I can still load cl-ppcre and other Edi-ware. Upon rolling back to 0.19.1, the same usocket package compiles and loads just fine. I have tried using the binary distribution of 0.20.0 as well as building my own, with the same result. There does not seem to be anything wrong with the usocket package definition itself. Has anyone else seen this or know what is going on? Here is the output of 0.20.0:
[…]
Seemingly a bug in ABCL macro expansion for keyword arguments for which a value is NIL with additional arguments in the list.
For now, if you aren't using SBCL with the same usocket.asd you can patch usocket with the attached patch. […]
Filed as [ticket #101][1]. [1]: http://trac.common-lisp.net/armedbear/ticket/101 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
Hi Mark, Kevin, On Fri, Jun 25, 2010 at 11:21 AM, Mark Evenson <evenson@panix.com> wrote:
On 6/10/10 7:13 AM, Mark Evenson wrote:
On 6/9/10 8:20 PM, Kevin Raison wrote:
I just installed 0.20.0 and am now unable to load usocket, yet I can still load cl-ppcre and other Edi-ware. Upon rolling back to 0.19.1, the same usocket package compiles and loads just fine. I have tried using the binary distribution of 0.20.0 as well as building my own, with the same result. There does not seem to be anything wrong with the usocket package definition itself. Has anyone else seen this or know what is going on? Here is the output of 0.20.0:
[…]
Seemingly a bug in ABCL macro expansion for keyword arguments for which a value is NIL with additional arguments in the list.
For now, if you aren't using SBCL with the same usocket.asd you can patch usocket with the attached patch. […]
Filed as [ticket #101][1].
Thanks for the very nice (and small!) reproduction recipe. It took quite a bit before I understood what's happening here, but the regression has been fixed now! (On trunk/ that is.) Bye, Erik.
participants (4)
-
Erik Huelsmann -
Kevin Raison -
Mark Evenson -
Mark Evenson