[Openmcl-devel] 0.14.2/paserve problems?
gb at clozure.com
Sat May 8 16:47:41 PDT 2004
Someone reported this just as I was sending out the 0.14.2 release
announcement the other night; the fix is also in the main (0.14) CVS
Right at the moment, the 0.14 and 0.14-dev CVS trees are nearly identical;
as they start to diverge (and they generally do), it may wiser to look
for updates in the main tree (after a bunch of changes, the 0.14-dev sources
can get hard to bootstrap with the released lisp.)
So far, this seems to be the worst thing that's been reported; if nothing
else gets reported in the next few days, I'll try to put up 0.14.2-p1
binaries that incorporate this fix.
(People who use the SLIME Emacs interface may find that if they get
past the socket bugs, SLIME's backtrace doesn't work. The "low level
stack-walking changes that shouldn't be user-visible" that 0.14.2
introduced are visible to SLIME's backtrace. I'll try to work with
the SLIME developers to get this straightened out; it may be hard to
get it straightened out in a backward-compatible way.
On Sat, 8 May 2004, Greg Wuller wrote:
> I ran into the same problem with paserve (and slime). If you grab a
> copy of level-1/l1-sockets.lisp from the 0.14-dev cvs repository and
> rebuild the image everything works again.
> I believe the following is what you want (assuming you don't already
> have a copy of the development branch):
> Hope that helps,
More information about the Openmcl-devel