The default ebuild for dev-lisp/cl-aserve resp. dev-lisp/cl-acl-compat uses a cvs version from 2005-08-05, the alternative would be from 2005-02-20. But as you can see in [1], in the version of the default ebuild the new thread api of sbcl is used. However, when you look at [2], the thread api changed in 0.9.2.9, ie. in =dev-lisp/sbcl-0.9.2 (the default ebuild for SBCL) the old api is still used. As a result, acl-compat / aserve as of 2005-08-05 does not work with sbcl-0.9.2. Solutions: Either downgrade default ebuild for acl-compat / aserve, or upgrade sbcl's default one (especially as a new stable version of sbcl has just been releaed. See Bug #103899.) [1] http://cvs.sourceforge.net/viewcvs.py/portableaserve/portableaserve/acl-compat/sbcl/acl-mp.lisp?rev=1.15&view=markup [2] http://cvs.sourceforge.net/viewcvs.py/sbcl/sbcl/src/code/target-thread.lisp?rev=1.33&view=markup Reproducible: Always Steps to Reproduce: 1. 2. 3.
Thanks for the note. Upon committing the new ebuild for SBCL 0.9.4, I will mark =dev-lisp/sbcl-0.9.3 stable for some architectures (not ppc though due to Bug #99456, and not mips immediately due to not having direct access to it). This means that for the other architectures (ie. amd64, sparc and x86) the "default" (stable) ebuild will be 0.9.3 which should solve this bug.
Except for ppc and mips, the stable ebuild is now sbcl 0.9.3
