From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: "Léon Lain Delysid" <leon.lain.delysid@gmail.com>, 42002@debbugs.gnu.org
Subject: bug#42002: Bug: Signal kill during build
Date: Tue, 23 Jun 2020 23:26:11 +0200 [thread overview]
Message-ID: <871rm5zd70.fsf@gnu.org> (raw)
In-Reply-To: <20200622135144.GA9358@jasmine.lan> (Leo Famulari's message of "Mon, 22 Jun 2020 09:51:44 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Mon, Jun 22, 2020 at 03:47:08PM +0300, Efraim Flashner wrote:
>> The signal 9 (killed) makes me think a C++ program killed. I checked
>> wikipedia and it says the Banana Pi M3 has 2GB of RAM. Was there
>> anything else running at the time? 'guix pull' can be resource
>> intensive, especially on lower powered machines.
>
> I think it should be possible with 2GB of RAM, if you limit the number
> of concurrent builds.
>
> For example, something like `guix pull --max-jobs=1`.
>
> And I think the memory requirements should decrease with the recently
> released Guile 3.0.3:
>
> https://lists.gnu.org/archive/html/guile-devel/2020-06/msg00008.html
For the record, I’ve successfully run the following command on my A20
OLinuXino with a bit less than 1 GiB of RAM:
guix pull --commit=380c3e459b6ebf0077008886954ff881a0cc7924
It takes ages, but fortunately substitutes were available for this
revision.
Before substitutes were available, it went OOM (out of memory) as in
your case while building guix-system.drv.
‘guix pull’ is still barely usable on these low-end devices, though with
Guile 3.0.3 it’s better.
Ludo’.
prev parent reply other threads:[~2020-06-23 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 12:28 bug#42002: Bug: Signal kill during build Léon Lain Delysid
2020-06-22 12:47 ` Efraim Flashner
2020-06-22 12:53 ` Léon Lain Delysid
2020-06-23 0:38 ` Bonface M. K.
2020-06-23 5:57 ` Efraim Flashner
2020-06-23 14:03 ` Bengt Richter
2022-07-14 3:23 ` bug#42002: 'guix pull' build processes get SIGKILL on ARMv7 Maxim Cournoyer
2020-06-22 13:51 ` bug#42002: Bug: Signal kill during build Leo Famulari
2020-06-23 21:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rm5zd70.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42002@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=leon.lain.delysid@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.