From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 48963-done@debbugs.gnu.org
Subject: bug#48963: "guix build guix" halts after exhausting memory
Date: Wed, 23 Jun 2021 23:43:55 +0200 [thread overview]
Message-ID: <87zgvgtfxg.fsf@gnu.org> (raw)
In-Reply-To: <87im2dpoj3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 16 Jun 2021 22:01:20 +0200")
Hi,
Ludovic Courtès <ludo@gnu.org> skribis:
> Julien Lepiller <julien@lepiller.eu> skribis:
>> Can we instead break the build (at the Makefile level) into multiple
>> smaller chunks, that require less memory, in the same way (guix self)
>> works?
>
> Yes, that’s a good idea.
>
> Could you check the extent to which the attached patch helps on this
> machine?
>
> It doesn’t split as much as (guix self) does, only in three pieces, but
> hopefully that helps a bit. A side effect is that progress report is
> now off, but we can fix it later.
I pushed a variant of this patch, resorting to an ugly hack so that
compile-all.scm can still estimate progress. The estimate is correct if
you’re building all the .go files, not so much if you just do, say:
make
rm guix/cpio.go && make
because guix/cpio.scm is in the first module set, so it’ll think it’s
starting from scratch and display “0%”.
Fixing it is left as an exercise to the reader. :-)
It seemed more important to me to fix the memory exhaustion issue first.
Thanks,
Ludo’.
prev parent reply other threads:[~2021-06-23 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 22:23 bug#48963: "guix build guix" halts after exhausting memory Julien Lepiller
2021-06-11 22:30 ` Julien Lepiller
2021-06-16 20:01 ` Ludovic Courtès
2021-06-17 13:58 ` Julien Lepiller
2021-06-17 22:17 ` Julien Lepiller
2021-06-18 9:51 ` Ludovic Courtès
2021-06-18 10:52 ` Julien Lepiller
2021-06-20 21:00 ` Ludovic Courtès
2021-06-21 11:05 ` Julien Lepiller
2021-06-23 21:43 ` Ludovic Courtès [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=87zgvgtfxg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48963-done@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).