unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Adam Kandur <rndd@tuta.io>
Cc: help-guix@gnu.org
Subject: Re: problem with common lisp
Date: Thu, 22 Oct 2020 10:27:26 +0200	[thread overview]
Message-ID: <87pn5ahdht.fsf@yamatai> (raw)
In-Reply-To: <MKBqw4l--7-2@tuta.io>

[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]


Adam Kandur via <help-guix@gnu.org> skribis:

> hi everyone! 
> recently i started getting this error when i try to build any sbcl package:
> --------------------------------------------------------------------------------------------------------
> starting phase `build'
> Invoking sbcl: "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" 
> This is SBCL 2.0.9, 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 15 tid 15:
> Unhandled SIGILL at 0x52000e9d.
>
> Error opening /dev/tty: No such device or address
> Welcome to LDB, a low-level debugger for the Lisp runtime environment.
> ldb> command "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" failed with status 1
> --------------------------------------------------------------------------------------------------------
> dont understand what went wrong, package definitions are unchanged

Hi,

The "Unhandled SIGILL at 0x52000e9d" error looks like the one in [1].
You could try downgrading sbcl to 2.0.8 to see if the error disappears.

[1] https://www.reddit.com/r/sbcl/comments/j824cs/does_binary_209_require_some_fancy_x86/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2020-10-22  8:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 20:31 problem with common lisp Adam Kandur via
2020-10-21 21:44 ` zimoun
     [not found]   ` <MKC8lw5--3-2@tuta.io>
2020-10-21 22:51     ` zimoun
2020-10-24 15:59       ` Adam Kandur via
2020-10-24 16:35         ` Guillaume Le Vaillant
2020-10-24 16:43           ` Adam Kandur via
2020-10-24 17:02             ` Guillaume Le Vaillant
2020-10-22  8:27 ` Guillaume Le Vaillant [this message]
     [not found]   ` <MKFC0qb----2@tuta.io>
2020-10-22 12:28     ` Guillaume Le Vaillant

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn5ahdht.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=rndd@tuta.io \
    /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).