From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>, Guix-devel <guix-devel@gnu.org>,
"Marius Bakke" <marius@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>
Subject: Re: Rust on aarch64-linux
Date: Wed, 26 Oct 2022 12:01:45 +0300 [thread overview]
Message-ID: <Y1j3edHqmaLJhMkd@3900XT> (raw)
In-Reply-To: <Y1RRGiJDwXvhfX5q@3900XT>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
On Sat, Oct 22, 2022 at 11:22:50PM +0300, Efraim Flashner wrote:
> On Fri, Oct 21, 2022 at 10:51:59AM +0200, Ludovic Courtès wrote:
> > Hello,
> >
> > Efraim Flashner <efraim@flashner.co.il> skribis:
> >
> > > I'm not sure there is a bug report, I didn't see it either. It looks
> > > like when I bumped rust-bootstrap from 1.39 to 1.54 we lost aarch64
> > > support. I've bumped mrustc on staging and successfully performed a
> > > qemu-binfmt build of rust-bootstrap for aarch64 on my x86_64 box. I was
> > > then able to use that to build rust-1.55 on actual aarch64 hardware, so
> > > I assume it's good, I just don't have the hardware to build
> > > rust-bootstrap for aarch64 natively.
> >
> > So the presumed fix involves bumping rust-bootstrap from 1.54 to 1.55,
> > is that right?
> >
> > That means we’ll have to rebuild on all architectures. This is
> > happening here:
> >
> > https://ci.guix.gnu.org/eval/739823
> >
> > Could you monitor it? If things go well, can we aim for a merge by next
> > Thursday?
>
> I think it looks good, but I'm not sure how to compare it to master.
> perhaps some Magic View™ using the guix data service?
I merged master into staging again and took a look at the build
failures. They seemed alright (and I restarted a few) and then merged
staging into master. Everything looks good from cuirass in relation to
the merging.
--
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-10-26 9:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07 9:49 ` Ludovic Courtès
2022-10-07 10:14 ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07 9:50 ` Ludovic Courtès
2022-10-07 9:53 ` Maxime Devos
2022-10-07 6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02 ` Ludovic Courtès
2022-10-10 7:57 ` Csepp
2022-10-12 20:40 ` Vagrant Cascadian
2022-10-13 15:06 ` Ludovic Courtès
2022-10-07 8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09 ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33 ` Efraim Flashner
2022-10-13 15:42 ` Christopher Baines
2022-10-20 13:49 ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07 ` Efraim Flashner
2022-10-21 8:51 ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42 ` Efraim Flashner
2022-10-22 20:22 ` Efraim Flashner
2022-10-26 9:01 ` Efraim Flashner [this message]
[not found] ` <87h6zyo811.fsf@gnu.org>
2022-10-21 8:43 ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21 9:30 ` Mathieu Othacehe
2022-10-31 17:40 ` Tobias Platen
2022-10-22 12:18 ` Release progress, week 2 Christopher Baines
2022-10-25 9:50 ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29 ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad 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=Y1j3edHqmaLJhMkd@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=marius@gnu.org \
--cc=othacehe@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.
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).