all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 37482@debbugs.gnu.org
Subject: bug#37482: Guix fails to build libreoffice
Date: Mon, 23 Sep 2019 02:45:35 +0200	[thread overview]
Message-ID: <20190923024535.39385299@kompiuter> (raw)
In-Reply-To: <8736gorzqn.fsf@nckx>

On Sun, 22 Sep 2019 19:45:52 +0200
Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> 2 GiB of RAM is simply not enough to build many packages these 
> days.  That's the world we live in.  There's nothing Guix can do 
> to change that.

Sad, guess I have to buy more RAM.

> You can restrict the number of parallel builds and jobs by 
> respectively passing --max-jobs=1 and --cores=1 to the daemon. 
> You can make this permanent by setting (extra-options …) in your 
> system configuration.

Cool, didn't know about this option.

> Even then, some complex executables will simply fail to link with 
> so little RAM.
> 
> Your issue is different: the exact same libreoffice might have 
> built fine if you had 4 GiB of RAM, or 3, or 5, or 2 with swap, 
> but only if your weren't also running any (Guix or other) builds 
> at the time, or watching a movie, or had the room thermostat 
> turned up, or use Gnome 3, all beneath a gibbous moon.  All these 
> things, and many more, will cause builds to fail or succeed 
> ‘randomly’.

I actually have a 10GB sized swap file created on an SSD and
defined in the config.scm, but it didn't help. I'm also using Mate, but
I can try without any DE. The only two things running in the background
were Mate, mate terminal, Guix and %desktop-services.

> I personally think the annoyances of ‘helpful’ warnings 
> (=extremely inaccurate guesses) would far outweigh any purported 
> benefit.
> 
> Kind regards,
> 
> T G-R

Is there a way to skip building libreoffice, if the substitute isn't
available?

>Or just how quickly it can destroy an SSD.

Even more fun... Waiting for a powerful libre computer from from the
ground, because running on old ThinkPads forever isn't the right
solution.


Thanks for explanations and help,

Jan Wielkiewicz

  parent reply	other threads:[~2019-09-23  0:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22 16:52 bug#37482: Guix fails to build libreoffice Jan Wielkiewicz
2019-09-22 17:45 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-22 18:28   ` Jesse Gibbons
2019-09-22 18:41     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-22 18:44       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-23  0:45   ` Jan [this message]
2019-09-26 20:04     ` Ludovic Courtès
2019-09-27 18:02       ` Jan
2019-09-28  9:31         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190923024535.39385299@kompiuter \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=37482@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.