[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with common lisp
From: |
Adam Kandur |
Subject: |
Re: problem with common lisp |
Date: |
Sat, 24 Oct 2020 17:59:44 +0200 (CEST) |
hi, i realized that i have this problem with sbcl itself, if i install sbcl in
my main profile (without any of my packages, only sbcl from guix channel) i
still got this error:
fatal error encountered in SBCL pid 1954 tid 1954:
Unhandled SIGILL at 0x52000e9d.
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb>
Oct 21, 2020, 22:51 by zimon.toutoune@gmail.com:
> Please keep help-guix CC. :-)
>
> On Wed, 21 Oct 2020 at 23:53, Adam Kandur <rndd@tuta.io> wrote:
>
>> hi, i mean that my packages for common lisp are same as one week ago when
>> everything worked. also i had same issues with packages from guix channel.
>> don't know about guix-deploy
>>
>
> I understand.
>
> First, since the package you are building is yours, more information
> is required to be able to find what is wrong. Idem about your
> channel.
>
>
> The questions in my previous email are:
>
> 1. could you provide the last version of Guix where it "worked"?
> 2. could you provide the current version of Guix where it is "broken"?
>
> The #1 means that you have to:
>
> a) "guix pull -l | grep guix". This will display all the previous
> versions of Guix you had (hoping that you have not deleted by running
> "guix gc" with some well-chosen options).
> From these versions (hashes), you can run:
>
> guix time-machine --commit=<hash> -- build -L paht/to/your/local/pkg sbcl-foo
>
> and see which worked and which not. The easiest is to go
> anti-chronological (start by your current Guix version and go
> backward).
>
> b) "guix describe" and probably attach the recipe of your broken
> package. For example it seems that one of your package is named
> "sbcl-deploy" since you have one item in the store named
> "/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497"
> and this package is not in "master", AFAICT.
>
>
> All the best,
> simon
>
Re: problem with common lisp, Guillaume Le Vaillant, 2020/10/22