From: Adam Faiz via Guix-patches via <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>
Cc: 75241@debbugs.gnu.org
Subject: [bug#75241] [PATCH] gnu: gerbil: Don't target the build machine.
Date: Thu, 2 Jan 2025 11:04:26 +0800 [thread overview]
Message-ID: <a753b30e-7a9e-47e5-88e7-1223467cd211@disroot.org> (raw)
In-Reply-To: <337a7cfc-e3b0-4c94-b0c1-a3b58fc24c97@disroot.org>
Hi jgart,
> Hi, thanks for the contribution.
>
> Can you explain the context and motivation around this change?
>
> It would help me in reviewing this.
>
> Thanks!
Sure! I wanted to try out Gerbil Scheme, so I installed the gerbil package. Unfortunately, using it's interpreter 'gxi' immediately gave an "Illegal instruction" error on my computer. After inspecting the configure script, I found that it defaults to compiling specifically for the CPU instructions available on the machine performing the build(-march=native). This leads to build results that aren't portable or reproducible across different machines of the same CPU architecture.
Avoiding this requires setting --enable-march to the empty string, which is only done for OpenBSD in the configure script, so the patch I sent sets this as a configure flag. It might be counterintuitive that there isn't a --disable-march option, but I wanted to fix the problem with the least work. If you feel there's a better way to solve the problem, please let me know.
>
> --
> all the best,
> jgart
Sincerely,
Adam
prev parent reply other threads:[~2025-01-02 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 11:24 [bug#75241] [PATCH] gnu: gerbil: Don't target the build machine Adam Faiz via Guix-patches via
2025-01-01 17:42 ` jgart via Guix-patches via
2025-01-02 3:04 ` Adam Faiz via Guix-patches via [this message]
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=a753b30e-7a9e-47e5-88e7-1223467cd211@disroot.org \
--to=guix-patches@gnu.org \
--cc=75241@debbugs.gnu.org \
--cc=adam.faiz@disroot.org \
--cc=jgart@dismail.de \
/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).