all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: phodina via <help-guix@gnu.org>
Subject: Re: Aarch64 build of rust-1.39.0 fails
Date: Tue, 4 Jan 2022 00:21:12 +0100	[thread overview]
Message-ID: <20220104002112.7928301e@primary_laptop> (raw)
In-Reply-To: <87k0g02deu.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

On Sun, 19 Dec 2021 21:55:21 -0500
Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> This is not a Rust but a (known) mrustc issue, which is used to
> bootstrap Rust starting at version 1.39.0.  It currently only supports
> x86_64, although the author is interested in enabling support for
> other architectures (a WIP).
So that's why it also fails on i686.

In that case would it be possible to revert to the way it
was before for non x86_64 architectures (so without mrustc), when it's
done to switch the remaining architectures to mrustc when they become
ready for that?

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-01-03 23:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 13:14 Aarch64 build of rust-1.39.0 fails phodina via
2021-12-17 16:37 ` Vagrant Cascadian
2021-12-20  2:55 ` Maxim Cournoyer
2021-12-22 10:51   ` phodina
2022-01-03 23:21   ` Denis 'GNUtoo' Carikli [this message]
2022-01-04 16:18     ` Maxim Cournoyer
2022-01-04 17:41       ` Denis 'GNUtoo' Carikli
2022-01-04 22:22         ` Maxim Cournoyer
2022-01-09 21:13           ` Denis 'GNUtoo' Carikli
2022-01-10 21:22             ` Maxim Cournoyer
2022-01-11 13:34               ` Efraim Flashner
2022-01-14 23:27                 ` Denis 'GNUtoo' Carikli
2022-01-18  4:36                   ` Maxim Cournoyer
2022-01-18  6:15                     ` Denis 'GNUtoo' Carikli

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=20220104002112.7928301e@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=help-guix@gnu.org \
    --cc=maxim.cournoyer@gmail.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.