From: Tamas Papp <tkpapp@gm...> - 2011-10-06 13:03:56
I am using the debian packages for sbcl (and sbcl-source), and I have
a problem with SLIME finding the definition for functions defined in
the SBCL source. Eg if I do M-. on copy-seq, the xref buffer starts
with "(No location)", and *slime-events* reports things like
(:error "Error: failed to find the WRITE-DATE of /build/sbcl-a405QP/sbcl-18.104.22.168/src/code/seq.lisp:\n No such file or directory"))
Is there a way I can tell an SBCL compiled by somebody else that its
sources are located in /usr/share/sbcl-source?
PS.: Should I report this as a bug?
PS.: $ dpkg -l 'sbcl*'
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
ii sbcl 2:22.214.171.124-1 Common Lisp compiler and development system
un sbcl-common <none> (no description available)
ii sbcl-doc 2:126.96.36.199-1 Documentation for Steel Bank Common Lisp
un sbcl-fasl-loader-78 <none> (no description available)
ii sbcl-source 2:188.8.131.52-1 Source code files for SBCL
Tamas Papp <tkpapp@...> wrote:
> I am using the debian packages for sbcl (and sbcl-source), and I have
> a problem with SLIME finding the definition for functions defined in
> the SBCL source.
That's not an answer to your question, but given the reactivity of
Debian these days, I think you'd be better off compiling your own
version of SBCL anyways. It's quite simple.
Resistance is futile. You will be jazzimilated.
Scientific site: http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com
On 6 October 2011 16:03, Tamas Papp <tkpapp@...> wrote:
> Is there a way I can tell an SBCL compiled by somebody else that its
> sources are located in /usr/share/sbcl-source?
Something along the lines of
(setf (logical-pathname-translations "SYS")
should do the trick.