unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Sébastien Lerique" <sl@eauchat.org>, 66249@debbugs.gnu.org
Subject: bug#66249: Building for armv7 fails
Date: Thu, 31 Oct 2024 14:16:23 -0400	[thread overview]
Message-ID: <CA+3U0Z=uRdU21-U=b+g_f1fXOo-0ZEe515YZEVMLHEq5Z+u+og@mail.gmail.com> (raw)
In-Reply-To: <87lecj5e20.fsf_-_@gmail.com>

On Tue, Oct 3, 2023 at 10:16 PM Maxim Cournoyer
<maxim.cournoyer@gmail.com> wrote:
>
> Hello,
>
> Sébastien Lerique <sl@eauchat.org> writes:
>
> > retitle 66249 Building rust-1.54 fails on armv7
>
> As you've found out, this is something that has to do with building rust
> on that architecture, more precisely building 'mrustc', which is used in
> Guix to boostrap rust.  The upstream issue would be this one I think:
> <https://github.com/thepowersgang/mrustc/issues/78>.  It's about GCC
> requiring more memory than 32 bit can address but the author mentioned a
> 2 GiB or something limit, I'm not sure what that is attributable to.
>
> If you want to solve this I'd recommend you get in touch with the mrustc
> author!  There is a #mrustc channel on Libera.chat IRC, as far as I
> recall.

Is there anything for Guix to do here or can the issue be closed?




  reply	other threads:[~2024-10-31 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  8:19 bug#66249: Building for armv7 fails Sébastien Lerique
     [not found] ` <handler.66249.B.16958899986945.ack@debbugs.gnu.org>
2023-09-28  8:36   ` bug#66249: Acknowledgement (Building for armv7 fails) Sébastien Lerique
2023-09-28 11:14     ` Sébastien Lerique
2023-10-04  2:14       ` bug#66249: Building for armv7 fails Maxim Cournoyer
2024-10-31 18:16         ` Greg Hogan [this message]
2024-10-31 22:13           ` Sébastien Lerique
2024-11-01  5:25             ` Maxim Cournoyer

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='CA+3U0Z=uRdU21-U=b+g_f1fXOo-0ZEe515YZEVMLHEq5Z+u+og@mail.gmail.com' \
    --to=code@greghogan.com \
    --cc=66249@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=sl@eauchat.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).