On Tue, Jul 17, 2012 at 9:23 PM, Sean Champ
<spchamp@me.com> wrote:
I have long promised to do an "official" port of quicklisp for MKCL but it is still near the top of my work stack,
just below "pushing MKCL 1.1.0 out the door" that I am currently hard at work on...
It was a straightforward patch, focusing mostly on sockets support. Basically I just copied the quicklisp implementation package definition for SBCL, with some minor revisions. I was testing it out, then, when I encountered the following error.
I'm not sure if the error may be a matter of the patched quicklisp - going by the debugger output, I'd like to assume it may be a matter of socket streams.
It looks like quicklisp implements its own HTTP client. Maybe there could be a workaround possible, somewhere in that client code?
I wasn't certain about sending the patch to the quicklisp developers, given this 'feature'. Looking at the debugger output, it looks like the error was in mkcl_safe_fclose failing on a socket-output-stream due to a bad FD. Here's the debugger output and backtrace.
This looks interesting to look at. Please, give me 24 to 48 hours to properly investigate it.
I don't think you should escalate this to the quicklisp people yet, it really looks like a MKCL private matter.
BTW, was there a reason for trying this with MKCL 1.0.1 rather than MKCL 1.1.0 RC1?
That would in fact be my first test since there was some move on the socket side between the two.