From: Christopher Howard <christopher@librehacker.com>
To: 49372@debbugs.gnu.org
Subject: bug#49372: lagrange: illegal instruction
Date: Sat, 03 Jul 2021 19:32:45 -0800 [thread overview]
Message-ID: <211fd2aad1f195944fa8305799382d8e2cfc90b9.camel@librehacker.com> (raw)
Hi, I've discovered lagrange is another one of those packages which, if I use a substitute, it gives the error "illegal instruction" when I try to run it. but if I download the source and build it
myself, I have no trouble running it. I'm certain without any research that this is a reproducibility error, due to native instructions not on my processor, but I could do the guix challenge if
somebody could remind me exactly how to tell guix to rebuild that one package from source.
christopher@nightshade ~$ neofetch --stdout
christopher@nightshade
----------------------
OS: Guix System b65af6ed9120234cf655e8e76317558cfbd02477 x86_64
Host: GA-880GM-UD2H
Kernel: 5.12.14-gnu
Uptime: 48 mins
Packages: 107 (guix-system), 103 (guix-user)
Shell: bash 5.0.16
Resolution: 1920x1200
DE: GNOME 3.34.5
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: kitty
CPU: AMD Athlon II X3 455 (3) @ 3.300GHz
GPU: NVIDIA GeForce 8400 GS Rev. 3
Memory: 1419MiB / 7957MiB
--
Christopher Howard
my gemini capsule: gemini://gem.librehacker.com
gemini browser: https://git.skyjake.fi/gemini/lagrange/releases
next reply other threads:[~2021-07-04 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 3:32 Christopher Howard [this message]
2021-07-04 12:18 ` bug#49372: lagrange: illegal instruction Maxime Devos
2021-07-04 12:24 ` Maxime Devos
2021-07-04 19:09 ` Efraim Flashner
2021-07-04 23:14 ` Christopher Howard
2021-07-05 0:40 ` Christopher Howard
2021-07-05 1:40 ` Christopher Howard
2021-07-05 6:11 ` Efraim Flashner
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=211fd2aad1f195944fa8305799382d8e2cfc90b9.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=49372@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).