[bknr-devel] Recursive locks problem on sbcl

[Hans Hübner]

Kamen, Hi,

sorry for putting you on hold for so long.  I did not have the time to
review your patch when you sent it, and it now does no longer apply
cleanly.

Generally, I would like to continue to be able to get a BKNR based
installation to run without having to turn to external sources, thus
the thirdparty/ directory.  I am aware that this is not a very good
solution, but to me, this is better than having to follow upstream
changes to thirdparty stuff all the time.  Also, I have no immediate
plans to upgrade my existing installations from cmucl-19c.  Can you
please re-send your patch as an attached file, against current BKNR?
Does the patched version run with cmucl-19c?

I will promptly apply and commit the patch if you send it soon.  Sorry
for the delay.

Thanks,
Hans

2007/10/2, Kamen TOMOV <kamen at cybuild.com>:
> On Tue, Oct 02 2007, Denis Mashkevich wrote:
>
> > Hi Hans,
> > the problem we've spoken of yesterday on irc (recursive lock attempt
> > warning on sbcl using bknr datastore) proved to be trivial to solve
> > - there is a primitive in sb-thread for exactly this case. I have
> > not tested it extensively yet, but it appears to work. The patch is
> > attached.
>
> Could you please elaborate on the problem? What happens with the
> datastore in SBCL without the patch?
>
> > FWIW, being unable to load some third-party libraries supplied with
> > bknr (mainly cxml and unit-test), I ditched thirdparty altogether,
> > installed all the newest versions of whatever bknr-indices and
> > bknr-datastore depend on, and both seem to work.
>
> Some time ago I wrote a patch that dumped cxml for the purpose of
> using cmucl-19d. Hans, do you think we can apply (some modified
> version of) it?
>
> Best regards,
>
> --
> Kamen
> _______________________________________________
> bknr-devel mailing list
> bknr-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/bknr-devel
>