Summary: | slime does not work | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Labhard <m.labhard> |
Component: | Current packages | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | emacs |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael Labhard
2005-11-21 19:42:15 UTC
(In reply to comment #0) BTW, Nickodemus was replying to an earlier message from Helmut Eller: "Try to delete the fasl files in ~/.slime/fasl and restart. There are sometimes compilation errors but fasl files are still generated and placed in that directory. We don't recompile if there's already a fasl file and so you don't see the compiler error message. Helmut." to which I replied that I had no ~/.slime dir. First port of call for problems should be the Gentoo bugzilla. There is no ~/.slime FASL cache because the Gentoo ports are created to use the general cache in /var/cache/common-lisp-controller. If you are using SBCL, try removing old FASLs from there using this command: rm -rf /var/cache/common-lisp-controller/<your-username>/sbcl/* Nope. Sorry. Did as you recommended but slime still hangs just were it did, after compiling a lot of other files. Any other ideas? The combination of running the rm command you specified and also unmerging and re-emerging slime has corrected the problem -- for unknown reasons. I'll just have to resolve this as "cantfix" since there's not much hope for reproducing the problem here. I just updated app-emacs/slime in portage to the latest CVS (2005-12-11). Perhaps you'll have less problems with it. |