unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: phodina via <help-guix@gnu.org>
Subject: Re: Aarch64 build of rust-1.39.0 fails
Date: Tue, 04 Jan 2022 11:18:31 -0500	[thread overview]
Message-ID: <871r1nv5ig.fsf@gmail.com> (raw)
In-Reply-To: <20220104002112.7928301e@primary_laptop> (Denis Carikli's message of "Tue, 4 Jan 2022 00:21:12 +0100")

Hi Denis,

Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> writes:

> 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?

Rust has been bootstrapped via mrustc since September 2018 (commit
3159ef7c99c646b78b04cedb1bd3525c301ef978); I don't think it supported
non-x86_64 back then, it's just that Rust wasn't as widely used as it is
today so it had a lesser impact.

The impact of the lack of Rust on non-x86_64 architectures has been
reduced on non-x86_64 architectures on the master branch by workarounds
such as using polkit-duktape in place of the regular polkit to avoid
requiring Rust for non-x86_64 architectures or an older librsvg that can
be used to build GTK without SVG support.

The i686 native build of rust 1.39 via mrustc nearly succeeds, but fails
due to GCC using too much memory (more than the 4 GiB limit imposed by
32 bit addressing).  With the growth of Rust, there's growing value in
contributing testing and patches to mrustc, so if you'd like to help
Rust on Guix, that's currently the best option to pursue (there's a
#mrustc channel on libera.chat where the mrustc author is often
available).  There's also a wip-cross-built-rust branch that I had
started; I stopped working on it after finding out rustc couldn't be
built statically; other than that it was working to build rust things on
non-x86_64 platforms.

Thanks,

Maxim


  reply	other threads:[~2022-01-04 16:18 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
2022-01-04 16:18     ` Maxim Cournoyer [this message]
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

  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=871r1nv5ig.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=GNUtoo@cyberdimension.org \
    --cc=help-guix@gnu.org \
    /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.
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).