From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: 37482@debbugs.gnu.org
Subject: bug#37482: Guix fails to build libreoffice
Date: Sun, 22 Sep 2019 20:41:22 +0200 [thread overview]
Message-ID: <871rw8rx65.fsf@nckx> (raw)
In-Reply-To: <db7edec055f648e5d94f43afd0c8b8a72b66737a.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Jesse Gibbons 写道：
>> 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.
Sure, I think I suggested that (I was serious about Gnome, too!).
People tend to underestimate just how slow swap is by several
orders of magnitude, though.
Not sure about LibreOffice, but I doubt you'll have much luck
building, say, Chromium with 2 GiB of physical RAM, with or
without swap — but I admit I haven't been crazy enough to try :-)
Another hack you can try is enabling 50% zstd zswap, but with 2
GiB of RAM and such an old CPU that too is far out in diminishing
returns territory. It could just crash your kernel.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-09-22 18:42 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 [this message]
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=871rw8rx65.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=37482@debbugs.gnu.org \
--cc=jgibbons2357@gmail.com \
--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 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).