From: Maxime Devos <maximedevos@telenet.be>
To: Christopher Howard <christopher@librehacker.com>, 49372@debbugs.gnu.org
Subject: bug#49372: lagrange: illegal instruction
Date: Sun, 04 Jul 2021 14:24:02 +0200 [thread overview]
Message-ID: <584642f94a035d91ce870c0b5bcd88c98f3bbcc1.camel@telenet.be> (raw)
In-Reply-To: <211fd2aad1f195944fa8305799382d8e2cfc90b9.camel@librehacker.com>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
Christopher Howard schreef op za 03-07-2021 om 19:32 [-0800]:
> 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.
To test reproducibility, you can also try
# To avoid building the dependencies
$ guix environment lagrange --system=i686-linux --no-grafts
$ (exit environment)
$ guix build lagrange --no-substitutes --system=i686-linux
$ guix challenge lagrange --system=i686-linux
Maybe the issue also exists for the iN86 architecture family ...
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-07-04 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 3:32 bug#49372: lagrange: illegal instruction Christopher Howard
2021-07-04 12:18 ` Maxime Devos
2021-07-04 12:24 ` Maxime Devos [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=584642f94a035d91ce870c0b5bcd88c98f3bbcc1.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49372@debbugs.gnu.org \
--cc=christopher@librehacker.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.