From: Christopher Howard <christopher@librehacker.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 49372@debbugs.gnu.org
Subject: bug#49372: lagrange: illegal instruction
Date: Sun, 04 Jul 2021 15:14:50 -0800 [thread overview]
Message-ID: <bf98c6af1e2351076be634675c0297541fe1eb96.camel@librehacker.com> (raw)
In-Reply-To: <YOIHheIRkG4AzT5V@3900XT>
Test it as a substitute?
--
Christopher Howard
my gemini capsule: gemini://gem.librehacker.com
gemini browser: https://git.skyjake.fi/gemini/lagrange/releases
On Sun, 2021-07-04 at 22:09 +0300, Efraim Flashner wrote:
> On Sat, Jul 03, 2021 at 07:32:45PM -0800, Christopher Howard wrote:
> > 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.
> >
>
> I found that there is a spot in the code where it tests if the compiling
> computer can support sse4.1, and if so then it enables it. I've added a
> configure-flag to disable that. Can you test the new version?
>
next prev parent reply other threads:[~2021-07-04 23:16 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
2021-07-04 19:09 ` Efraim Flashner
2021-07-04 23:14 ` Christopher Howard [this message]
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=bf98c6af1e2351076be634675c0297541fe1eb96.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=49372@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).