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: Mon, 10 Jan 2022 16:22:17 -0500 [thread overview]
Message-ID: <877db7p9py.fsf@gmail.com> (raw)
In-Reply-To: <20220109221318.0784d8fd@primary_laptop> (Denis Carikli's message of "Sun, 9 Jan 2022 22:13:18 +0100")
Hi Denis,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> writes:
> On Tue, 04 Jan 2022 17:22:02 -0500
> Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> Hi Denis,
> Hi,
>
>> Note that you'll want to use the latest commit available of mrustc, or
>> something recent enough like this in (gnu packages rust) as it
>> includes recent fixes to the (still failing) i686 build:
> With ./build-1.39.0.sh in mrustc, some help from #mrustc, and some local
> patches, I was able to get it build under 4GiB of RAM per process with
> an x86_64 kernel (by removing -O2 and -g), but it fails for 3GiB of RAM
> per process (i686 kernel) no mater what options are passed to it.
Thank you for doing the experiment and sharing the result! I've relayed
it to mrustc's author here:
https://github.com/thepowersgang/mrustc/issues/78, I hope you don't
mind.
> My issue is that claws-mail now depend on rust (it didn't before). As
> several other pakcages also fails on i686 (failing tests), and that I
> also hit a Guix bug, it's hard for me to fix it as everything is
> broken and I need to do workarounds on workarounds.
The situation with Rust on Guix is far from satisfactory, and the usage
of Rust continues to expand, we'll have to find solutions. GCC-rust
seems like a good candidate to help us bootstrap for more platforms, but
it isn't ready yet. mrustc is the current best option; cross-building
rust could be another thing to do (there's a wip-cross-built-rust branch
that I had started to explore doing this), but it's a messier path.
> What do I need to revert (locally?) to make claws-mail not depend on
> rust (for i686)?
I don't see this relationship locally:
$ guix graph --path claws-mail rust
$ guix describe
5b95cad85018e64f2a34ef950dd2e5434d07cfc0
But looking at the package definition, it explicitly depends on librsvg,
which is a Rust-powered library. You could try to make this input
conditional (e.g., add it only when the system is x86_64), if claws-mail
can be built without it.
Thanks,
Maxim
next prev parent reply other threads:[~2022-01-10 21:29 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
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 [this message]
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=877db7p9py.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).