I was happily using SBCL-0.8.19 together with Emacs-21.4 and Slime-1.0.20050207. However, it appears that something has gone bad with SBCL as a result of a hard system crash. (The electric company unexpectedly cut power to my neighborhood to do some maintenance work.)
Upon restarting my system SBCL was unuseable. I did the following in an attempt to cleanly reinstall SBCL-0.8.19: - unmerged and re-emerged the dependencies common-lisp-controller-4.12 and cl-asdf-1.86. - (I can't remember whether I properly unmerged SBCL itself, but I pretty sure I did.) - removed the tree rooted at /var/tmp/portage/sbcl-0.8.19 as well as the sbcl distfiles under /usr/portage/distfiles. With all that, SBCL-0.8.19 still fails to build and I get this: < transcript > //entering make-target-2.sh //doing warm init This is SBCL 0.8.19, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. fatal error encountered in SBCL pid 21820: maximum interrupt nesting depth (32) exceeded The system is too badly corrupted or confused to continue at the Lisp level. If the system had been compiled with the SB-LDB feature, we'd drop into the LDB low-level debugger now. But there's no LDB in this build, so we can't really do anything but just exit, sorry. real 0m14.888s user 0m11.640s sys 0m1.750s </ transcript > On my (ancient) system it takes about 1 hr and 10 mins after starting the emerge to get to this point. I've tried reemerging several times now with the same result each time. I really don't want to invest days worth of time in trying to learn and use LDB unless there is no other alternative. Clearly, there is something different about my system now which prevents emerging SBCL whereas it was successful before. (BTW, I also did an "equery depgraph" for SBCL and received a horrifyingly long list of packages - must have been damn near everything that I've ever installed aside from kde.) Given this sob story, can anyone suggest a plan of action to get my SBCL-0.8.19 working once again? -- [email protected] mailing list
