all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tim Johann <t1m@phrogstar.de>
Cc: 62231-done@debbugs.gnu.org, Philip McGrath <philip@philipmcgrath.com>
Subject: bug#62231: Chez Scheme for Racket build on aarch64 (patch attached)
Date: Sun, 26 Mar 2023 16:26:33 +0200	[thread overview]
Message-ID: <87ilenbnc6.fsf_-_@gnu.org> (raw)
In-Reply-To: <87r0tdq51d.fsf@phrogstar.de> (Tim Johann's message of "Fri, 24 Mar 2023 21:03:19 +0100")

Hi,

Tim Johann <t1m@phrogstar.de> skribis:

> commit e3c514db745d48e5ef7f7abb7b45037341298b17
> Author: Tim Johann <t1m@phrogstar.de>
> Date:   Fri Mar 24 21:09:52 2023 +0100
>
>     gnu: chez-scheme-for-racket-bootstrap-bootfiles: change for aarch64.
>     
>     * gnu/packages/chez.scm (chez-scheme-for-racket-bootstrap-bootfiles):
>       Temporary change for build on aarch64, making racket available on aarch64.
>       Architecture autodetect in rktboot only addresses x86 archs, so far.
>       This work-around sets the architecture, looked up in translation table,
>       explicitly.  The long term solution should be to fix rktboot to include
>       other natively supported architectures in the autodetect mechanism.
>         cf. https://github.com/racket/racket/issues/3948
>       [arguments] use --machine even when architecture is supported by Racket's
>       fork of ChezScheme.

Applied!

Thank you Tim, and thanks Philip for reviewing.

Tim: please use ‘git format-patch’ in the future; the format here cannot
be ingested as-is by ‘git am’.

Ludo’.




      parent reply	other threads:[~2023-03-26 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 23:23 [bug#62231] Chez Scheme for Racket build on aarch64 (patch attached) Tim Johann
2023-03-24  1:36 ` Philip McGrath
2023-03-24 20:03   ` Tim Johann
2023-03-25  5:36     ` Philip McGrath
2023-03-26 14:26     ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ilenbnc6.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=62231-done@debbugs.gnu.org \
    --cc=philip@philipmcgrath.com \
    --cc=t1m@phrogstar.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 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.