2011/2/28 Nikodemus Siivola <nikodemus@...>:
> 2011/2/27 Slobodan Milnović <slobodan.milnovic@...>:
>> Just tried both my app and weblocks demo app that comes with weblocks,
>> using 188.8.131.52. Same error. Like I said, after 1.0.43, every release
>> version I have tried generates the same error. One more person
> I'm officially confused. I was able to reproduce the issue, and have
> fixed it in SBCL 184.108.40.206, where weblocks-demo now works for me --
> but the regression I found was in 220.127.116.11, so the only release
> affected should have been 1.0.46.
> So if the version Weblocks currently in Quicklisp has generated this
> error with weblocks-demo in 1.0.45 and 1.0.44, then something else is
> the matter as well.
> Can you confirm that the error happens to you with 1.0.45 and 1.0.44 as well?
Yes, I can. Standard procedure - download release version tar.bz2
source archive from http://www.sbcl.org, unpack, sh make.sh, sh install.sh
(as root of course), start emacs, slime, (asdf... 'weblocks-demo),
(weblocks-demo:start...) and try to connect to it using an browser.
When I first did the update of all of the libraries to the latest
upstream version (including weblocks-dev and sbcl 18.104.22.168), I had
that error. Since there were issues with CLX before, I guessed that
you guys enforced something that previously was optional, so while
waiting for the resolution by weblocks team, I have tried to revert to
the older version. I have tried release versions 1.0.45 and 1.0.44,
but I got it working only with 1.0.43.
But! I was using clbuild at that time, the old version, not the new
version that uses quicklisp. I've even tried this weekend using the
clbuild2, but this time only with the 22.214.171.124, and there was the
same error, as I have reported in the previous e-mail. I don't know if
that makes an difference.
I'll try it tonight when I get home and let you know the results.
P.S. Why did weblocks-demo worked with trace and without it didn't?
Does trace do something extra to to the sbcl environment?