From: "André Batista" <nandre@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 53506@debbugs.gnu.org
Subject: bug#53506: guix-packages-base.drv leads to segfault on i686-linux
Date: Fri, 11 Feb 2022 21:28:41 -0300 [thread overview]
Message-ID: <Ygb9R3+eUGQsPHEi@andel> (raw)
In-Reply-To: <8735kue3r8.fsf@gnu.org>
Hi Ludo!
seg 07 fev 2022 às 23:00:27 (1644285627), ludo@gnu.org enviou:
> Hi!
>
> An update: with changes made in Guile “main” over the last couple of
> weeks, memory consumption is 20% lower and compilation is 20% faster
> compared to 3.0.7 (on x86_64):
>
> To be continued…
I don't know if it is of any help, but after
'076e825dc5d585943ce820a279fffe4af09757fb' I could pull again after
a couple of weeks hitting this bug. Thanks a lot!
Previously I had tried to move rust-tokio* package definitions to
another file but it wasn't enough to work around it.
While parsing crates-io.scm, it also occured to me to try to
create a 'crates-crypto.scm' and move all crypto related definitions
there. Would you think this to be useful even after you get to the
solution you've been chasing? Are there any guix currently
working on chopping crates-io.scm down?
Cheers!
next prev parent reply other threads:[~2022-02-12 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:56 bug#53506: guix-packages-base.drv leads to segfault on i686-linux Ludovic Courtès
2022-01-24 17:15 ` Ludovic Courtès
2022-02-07 22:00 ` Ludovic Courtès
2022-02-08 14:03 ` Maxim Cournoyer
2022-02-12 0:28 ` André Batista [this message]
2022-02-12 14:24 ` Ludovic Courtès
2022-07-18 20:12 ` Ludovic Courtès
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=Ygb9R3+eUGQsPHEi@andel \
--to=nandre@riseup.net \
--cc=53506@debbugs.gnu.org \
--cc=ludo@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).