From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: SLIME and SBCL (Common Lisp)
Date: Sun, 27 Jun 2021 16:16:56 +0200 [thread overview]
Message-ID: <87im1zpf3b.fsf@zoho.eu> (raw)
In-Reply-To: 87wnqfe9el.fsf@zoho.eu
>> Trying to get SLIME and SBCL Common Lisp up-and-running but
>> my old stuff won't wort. It gets stuck on the count-up
>> connection phase.
>>
>> I installed slime and sbcl from the Debian repos [...]
>
> I had an old installation from MELPA as well, so that was
> what got used... dammit.
Yes, now it evals and byte-compile is fine but now the error
message is instead
(progn (load "/usr/share/common-lisp/source/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.111300"))
This is SBCL 2.1.1.debian, 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 111468 tid 111468:
invalid magic number in core: f145342434c should have been 5342434c
Process inferior-lisp exited abnormally with code 1
(progn (load "/usr/share/common-lisp/source/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.111300"))
This is SBCL 2.1.1.debian, 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 111854 tid 111854:
invalid magic number in core: f145342434c should have been 5342434c
Process inferior-lisp exited abnormally with code 1
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-06-27 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 6:05 SLIME and SBCL (Common Lisp) Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 13:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 14:16 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-06-27 18:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-28 6:41 ` Jean Louis
2021-06-28 10:30 ` Arthur Miller
2021-06-28 14:03 ` Jean Louis
2021-07-06 6:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 6:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 6:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 20:31 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im1zpf3b.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).