From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
55848@debbugs.gnu.org, Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
Subject: bug#55848: [cuirass] workers stalled
Date: Tue, 21 Jun 2022 01:32:33 -0400 [thread overview]
Message-ID: <87zgi67f9q.fsf@gmail.com> (raw)
In-Reply-To: <40c9de93c11d0b93a2df2b23ef6d1a4b56eeac0b.camel@telenet.be> (Maxime Devos's message of "Mon, 20 Jun 2022 15:02:55 +0200")
Hi Maxime,
Maxime Devos <maximedevos@telenet.be> writes:
> Maxim Cournoyer schreef op zo 19-06-2022 om 22:39 [-0400]:
>> There was also an attempt to cross-compile a rust/cargo bootstrap seed
>> for other architectures (branch: wip-cross-built-rust) but due to
>> complications with building rust as a static archive (it relies on
>> dynamic linking for its macro expand crates), the effort stalled.
>
> FWIW, has it been considered to cross-compile rust non-statically
> (not as a seed, just as an input cross-compiled from another system)?
> Doesn't help for people that cannot offload to x86_64 and don't have
> substitutes from ci.guix.gnu.org or such enabled, but could still be an
> improvement.
This already works, on the branch. One of the patches carried there
that made it possible has been merged upstream too. The issue is that
to offer a useful cross-compiled rust on non-x86_64 systems, you need to
move it from system domains; the clean way to do this is to archive a
static binary that depends on nothing else somewhere, and extract it in
a package for the target architecture.
Currently it's not cleanly self-contained because it still references
GCC libraries.
Maxim
prev parent reply other threads:[~2022-06-21 5:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:31 bug#55848: [cuirass] workers stalled Mathieu Othacehe
2022-06-08 19:07 ` Greg Hogan
2022-06-11 10:44 ` Tom Fitzhenry
2022-06-12 13:33 ` Ludovic Courtès
2022-06-12 16:10 ` Ricardo Wurmus
2022-06-12 20:22 ` Ludovic Courtès
2022-08-10 13:46 ` bug#55848: AArch64 honeycomb machines aren’t building stuff Ludovic Courtès
2022-08-10 17:55 ` Ricardo Wurmus
2022-08-11 14:06 ` bug#55848: [cuirass] workers stalled Ludovic Courtès
2022-08-29 13:30 ` bug#55848: AArch64 Honeycomb builders are inactive Ludovic Courtès
2022-06-19 2:07 ` bug#55848: [cuirass] workers stalled Tom Fitzhenry
2022-06-20 2:39 ` Maxim Cournoyer
2022-06-20 2:44 ` Tom Fitzhenry
2022-06-20 13:02 ` Maxime Devos
2022-06-21 5:32 ` Maxim Cournoyer [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
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=87zgi67f9q.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=55848@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=othacehe@gnu.org \
--cc=tom@tom-fitzhenry.me.uk \
/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).