[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#42002: Bug: Signal kill during build

From: Ludovic Courtès
Subject: bug#42002: Bug: Signal kill during build
Date: Tue, 23 Jun 2020 23:26:11 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

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

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]