From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
37482@debbugs.gnu.org,
Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Subject: bug#37482: Guix fails to build libreoffice
Date: Sun, 22 Sep 2019 12:28:45 -0600 [thread overview]
Message-ID: <db7edec055f648e5d94f43afd0c8b8a72b66737a.camel@gmail.com> (raw)
In-Reply-To: <8736gorzqn.fsf@nckx>
On Sun, 2019-09-22 at 19:45 +0200, Tobias Geerinckx-Rice via Bug reports for
GNU Guix wrote:
> Jan,
>
> Thanks for the report, and sorry you had to learn this the hard
> way.
>
> Jan Wielkiewicz 写道:
> > I've recently tried to reconfigure my system, but after about 3
> > hours
> > of building libreoffice, the system froze for 2 hours and then
> > guix
> > threw:
>
> […]
>
> > g++: internal compiler error: Killed (program cc1plus)
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <http://gcc.gnu.org/bugs.html> for instructions.
>
> This message and the freezing above is a tell-tale sign of OOM
> (out-of-memory). If you check your dmesg or /var/log/messages at
> that time, I'm almost certain you'll see the OOM killer plot its
> dastardly deeds.
>
> > My system is an old ThinkPad with 2GB of RAM and Intel Centrino
> > Duo
> > processor, but I'm unsure if this was the cause of the build
> > failing.
>
> You may be sure.
>
> 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.
>
> 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.
>
> Even then, some complex executables will simply fail to link with
> so little RAM.
You can get around too little RAM by using swap, correct? Partition ~8GB as
swap and add (swap-devices) in the configuration.
next prev parent reply other threads:[~2019-09-22 18:29 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 [this message]
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
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
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=db7edec055f648e5d94f43afd0c8b8a72b66737a.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=37482@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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).