From: Mark H Weaver <mhw@netris.org>
To: Chris Marusich <cmmarusich@gmail.com>,
Ricardo Wurmus <rekado@elephly.net>,
Christopher Baines <mail@cbaines.net>,
Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: core-updates: Emacs is only supported on x86_64-linux?
Date: Tue, 09 Mar 2021 19:05:27 -0500 [thread overview]
Message-ID: <87blbrj2jh.fsf@netris.org> (raw)
In-Reply-To: <87v9a04u2o.fsf@gmail.com>
Hi Chris,
Chris Marusich <cmmarusich@gmail.com> writes:
> Actually, I've realized that that patch wasn't quite right. I've
> attached a corrected version to this email.
>
> Although the %current-system parameter will look like "x86_64-linux"
> because it's a Guix system name, the %current-target-system parameter
> will look like "x86_64-linux-gnu" (or whatever the user happens to
> supply, e.g. via the --target option of "guix build") because it's a GNU
> triplet.
Indeed, good catch.
> The attached patch accomplishes the same goal as before, but
> it uses string-prefix? to check whether we're building for an x86_64
> machine, rather than matching on an exact string.
Your proposed patch looks good to me, as a temporary measure to make
Guix a bit more usable on non-Intel systems until we get Rust working on
them. I would be in favor of pushing it to 'core-updates'.
Thanks!
Mark
next prev parent reply other threads:[~2021-03-10 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 7:56 core-updates: Emacs is only supported on x86_64-linux? Chris Marusich
2021-03-07 10:46 ` Mark H Weaver
2021-03-07 23:40 ` Leo Famulari
2021-03-08 2:53 ` Chris Marusich
2021-03-08 5:29 ` Mark H Weaver
2021-03-08 7:14 ` Ricardo Wurmus
2021-03-10 0:09 ` Mark H Weaver
2021-03-08 7:19 ` Ricardo Wurmus
2021-03-09 6:04 ` Chris Marusich
2021-03-09 8:20 ` Chris Marusich
2021-03-10 0:05 ` Mark H Weaver [this message]
2021-03-08 22:33 ` Christopher Baines
2021-03-09 23:47 ` Mark H Weaver
2021-03-07 13:41 ` Christopher Baines
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=87blbrj2jh.fsf@netris.org \
--to=mhw@netris.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=mail@cbaines.net \
--cc=rekado@elephly.net \
/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).