From: Efraim Flashner <efraim@flashner.co.il>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 54580@debbugs.gnu.org
Subject: [bug#54580] [PATCH staging?] gnu: mrustc: Update to 0.10.
Date: Mon, 9 May 2022 17:22:50 +0300 [thread overview]
Message-ID: <YnkjuptjWCtpJV5p@3900XT> (raw)
In-Reply-To: <87h77kajc9.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Sat, Mar 26, 2022 at 02:16:06PM +0000, Pierre Langlois wrote:
>
> Pierre Langlois <pierre.langlois@gmx.com> writes:
>
> > [[PGP Signed Part:Undecided]]
> > Hi Guix!
> >
> > Good news everyone, I managed to get a aarch64 build of Rust by updating
> > mrustc to 0.10! Sadly, i686 is still unsupported, due to the build
> > using too much memory, it must be the same for other 32-bit architectures.
> >
> > I tested this on a pinebookpro which only has 4G of RAM, I had to attach
> > 16G of swap for the initial rust@1.39 build to succeed, then the whole
> > rust chain took about 5 days! I also tested on my x86_64 desktop.
> >
> > Here's the patch! After it we should be able to follow-up and enable
> > Gnome and friends.
> >
> > That being said, I wasn't entirely sure where this patch should go,
> > ideally it would be good to have a staging branch rather than
> > core-updates, WDYT? Maybe we can do this along with a rust version
> > update?
> >
> > PS: I also tried to build rust 1.54 with the new mrustc update, to
> > shorten the chain, but I've not had any successes with it yet.
> >
Go ahead and push it to staging. I have high on my TODO list to get it
working with 1.54.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-09 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 13:27 [bug#54580] [PATCH staging?] gnu: mrustc: Update to 0.10 Pierre Langlois
2022-03-26 14:16 ` Pierre Langlois
2022-03-26 14:58 ` Maxime Devos
2022-03-26 15:05 ` Pierre Langlois
2022-05-09 14:22 ` Efraim Flashner [this message]
2022-05-09 22:12 ` bug#54580: " Pierre Langlois
2022-03-26 15:09 ` [bug#54439] [bug#54580] " Maxime Devos
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=YnkjuptjWCtpJV5p@3900XT \
--to=efraim@flashner.co.il \
--cc=54580@debbugs.gnu.org \
--cc=pierre.langlois@gmx.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.