Does not build on SBCL today
quicklisp opened this issue · comments
I get this when trying to build:
; file: /home/xach/quicklisp-controller/dist/build-cache/wuwei/d9d63b8a4fec01b8a365e5e6b3b85f02957135b5/wuwei-20120604-git/src/session.lisp
; in: DEFUN SESSION-DEBUG-PAGE
; (WUWEI:AJAX-CONTINUATION NIL
; (WUWEI:WITH-SESSION (WUWEI::REQ WUWEI::ENT)
; (WUWEI:DELETE-SESSION WUWEI::*SESSION* TYPE)
; (WUWEI:WITH-SESSION-RESPONSE (WUWEI::REQ WUWEI::ENT :NO-SAVE? T
; :CONTENT-TYPE "text/javascript")
; (WUWEI:RENDER-UPDATE
; (:REDIRECT "/session-debug")))))
; --> LET WUWEI:PUBLISH-AJAX-FUNC WUWEI:PUBLISH-AJAX-UPDATE
; --> WUWEI::PUBLISH-TEMPORARILY MT:NAMED-LAMBDA LABELS BLOCK LET*
; --> WUWEI:WITH-SESSION LET* WUWEI::WITH-SESSION-VARIABLES LET PROGV LET
; --> UNWIND-PROTECT FLET BLOCK MULTIPLE-VALUE-BIND MULTIPLE-VALUE-CALL BLOCK
; --> SB-C::%WITHIN-CLEANUP RETURN-FROM PROGN UNWIND-PROTECT FLET BLOCK
; --> MULTIPLE-VALUE-BIND MULTIPLE-VALUE-CALL BLOCK SB-C::%WITHIN-CLEANUP
; --> RETURN-FROM SETQ THE PROGN WUWEI:WITH-HTTP-RESPONSE-AND-BODY
; --> NET.ASERVE:WITH-HTTP-RESPONSE LET* CATCH BLOCK SB-C::%WITHIN-CLEANUP
; --> ACL-COMPAT.MP:WITH-TIMEOUT HANDLER-CASE SB-INT:DX-FLET FLET BLOCK
; --> WITH-TIMEOUT SB-INT:DX-FLET FLET BLOCK PROGN NET.ASERVE:WITH-HTTP-BODY
; --> LET ACL-COMPAT.EXCL:IF* COND IF PROGN LET PROGN
; --> WUWEI:WITH-AJAX-ERROR-HANDLER
; ==>
; (WUWEI::FNAME)
;
; caught WARNING:
; function called with zero arguments, but wants exactly two
; See also:
; The ANSI Standard, Section 3.2.2.3
Strange, it builds on SBCL fine for me.
I can't really interpret that error message -- which function does it claim
is getting the wrong # of arguments?
Mike
On Mon, Jun 4, 2012 at 7:17 AM, Zach Beane <
reply@reply.github.com
wrote:
I get this when trying to build:
; file:
/home/xach/quicklisp-controller/dist/build-cache/wuwei/d9d63b8a4fec01b8a365e5e6b3b85f02957135b5/wuwei-20120604-git/src/session.lisp
; in: DEFUN SESSION-DEBUG-PAGE
; (WUWEI:AJAX-CONTINUATION NIL
; (WUWEI:WITH-SESSION (WUWEI::REQ WUWEI::ENT)
; (WUWEI:DELETE-SESSION WUWEI::SESSION TYPE)
; (WUWEI:WITH-SESSION-RESPONSE (WUWEI::REQ WUWEI::ENT :NO-SAVE?
T
; :CONTENT-TYPE "text/javascript")
; (WUWEI:RENDER-UPDATE
; (:REDIRECT "/session-debug")))))
; --> LET WUWEI:PUBLISH-AJAX-FUNC WUWEI:PUBLISH-AJAX-UPDATE
; --> WUWEI::PUBLISH-TEMPORARILY MT:NAMED-LAMBDA LABELS BLOCK LET*
; --> WUWEI:WITH-SESSION LET* WUWEI::WITH-SESSION-VARIABLES LET PROGV
LET
; --> UNWIND-PROTECT FLET BLOCK MULTIPLE-VALUE-BIND MULTIPLE-VALUE-CALL
BLOCK
; --> SB-C::%WITHIN-CLEANUP RETURN-FROM PROGN UNWIND-PROTECT FLET BLOCK
; --> MULTIPLE-VALUE-BIND MULTIPLE-VALUE-CALL BLOCK
SB-C::%WITHIN-CLEANUP
; --> RETURN-FROM SETQ THE PROGN WUWEI:WITH-HTTP-RESPONSE-AND-BODY
; --> NET.ASERVE:WITH-HTTP-RESPONSE LET* CATCH BLOCK
SB-C::%WITHIN-CLEANUP
; --> ACL-COMPAT.MP:WITH-TIMEOUT HANDLER-CASE SB-INT:DX-FLET FLET BLOCK
; --> WITH-TIMEOUT SB-INT:DX-FLET FLET BLOCK PROGN
NET.ASERVE:WITH-HTTP-BODY
; --> LET ACL-COMPAT.EXCL:IF* COND IF PROGN LET PROGN
; --> WUWEI:WITH-AJAX-ERROR-HANDLER
; ==>
; (WUWEI::FNAME)
;
; caught WARNING:
; function called with zero arguments, but wants exactly two
; See also:
; The ANSI Standard, Section 3.2.2.3
Reply to this email directly or view it on GitHub:
#13
The FNAME function.
FNAME isn't (supposed to be) a function.
Here's what the macroexpansion of the ajax-continuation form is supposed to
be (from line 399 in session.lisp). I'm guessing it is something else in
your universe, can you see?
(LET ((FNAME (STRING+ "/ajax/" "g" "/" (FAST-STRING (INCF
AJAX-COUNTER)))))
(PUBLISH-AJAX-FUNC (:PATH FNAME :CONTENT-TYPE "text/javascript") NIL
(WITH-SESSION (REQ ENT)
(DELETE-SESSION SESSION TYPE)
(WITH-SESSION-RESPONSE (REQ ENT :NO-SAVE? T
:CONTENT-TYPE
"text/javascript")
(RENDER-UPDATE
(:REDIRECT "/session-debug"))))
(UNPUBLISH-PATH FNAME))
FNAME)
On Mon, Jun 4, 2012 at 8:06 AM, Zach Beane <
reply@reply.github.com
wrote:
The FNAME function.
Reply to this email directly or view it on GitHub:
#13 (comment)
Hmm, I can't reproduce it on more than one system. I'll try to figure out what's going on and get back to you.
Ok, I can reproduce it like this:
cd ~/quicklisp/local-projects
git clone git://github.com/mtravers/wuwei.git
sbcl --non-interactive --eval "(ql:quickload :wuwei :verbose t)"
I get that in SBCL 1.0.56 and 1.0.51.
A possible clue is a preceding style warning:
; caught STYLE-WARNING:
; WITH-SESSION-VARIABLES is being redefined as a macro when it was previously assumed to be a function.
The full log is here: http://xach.com/tmp/wuwei-failure.txt
Well, I can't figure out what is going on, but this is a non-essential part
of the package, so maybe I will just turn it off in SBCL with a compile
flag unless you have a better idea. I've run the package in CCL and ACL,
and it seems to work there.
Mike
On Mon, Jun 4, 2012 at 11:07 AM, Zach Beane <
reply@reply.github.com
wrote:
Ok, I can reproduce it like this:
cd ~/quicklisp/local-projects
git clone git://github.com/mtravers/wuwei.git
sbcl --non-interactive --eval "(ql:quickload :wuwei :verbose t)"I get that in SBCL 1.0.56 and 1.0.51.
A possible clue is a preceding style warning:
; caught STYLE-WARNING:
; WITH-SESSION-VARIABLES is being redefined as a macro when it was
previously assumed to be a function.The full log is here: http://xach.com/tmp/wuwei-failure.txt
Reply to this email directly or view it on GitHub:
#13 (comment)
What version of SBCL are you using?
1.0.45, on Mac. I could try upgrading.
On Tue, Jun 5, 2012 at 5:21 AM, Zach Beane <
reply@reply.github.com
wrote:
What version of SBCL are you using?
Reply to this email directly or view it on GitHub:
#13 (comment)
Ahh, that seems likely. 1.0.45 was not as aggressive about detecting invalid argument counts in function call sites.
I hope to make a new release tomorrow - what do you think the resolution on this issue will be?
I'll try to give it some attention today.
On Fri, Jun 8, 2012 at 7:41 AM, Zach Beane <
reply@reply.github.com
wrote:
I hope to make a new release tomorrow - what do you think the resolution
on this issue will be?
Reply to this email directly or view it on GitHub:
#13 (comment)
Give it a try now.
On Fri, Jun 8, 2012 at 7:41 AM, Zach Beane <
reply@reply.github.com
wrote:
I hope to make a new release tomorrow - what do you think the resolution
on this issue will be?
Reply to this email directly or view it on GitHub:
#13 (comment)
Works, thanks!
Should be fixed now.