unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: bo0od <bo0od@riseup.net>
Cc: 47717@debbugs.gnu.org
Subject: bug#47717: guix becomes unresponsive while building the 'vigra' package
Date: Tue, 13 Apr 2021 13:35:56 -0400	[thread overview]
Message-ID: <YHXWfNAWojS67oXE@jasmine.lan> (raw)
In-Reply-To: <73e4e511-b66a-e62b-7ce8-bb6029ef0d2c@riseup.net>

On Tue, Apr 13, 2021 at 11:03:50AM +0000, bo0od wrote:
> 4GB DDR3 rams, i7 4th generation , 20GB for Guix about 9GB swap
> 
> If this is not enough to install simple common used packages like
> libreoffice or onionshare..etc then this is big issue if guix considered to
> be targeting average users.
> 
> In Qubes distro 4GB is worthless/nothing the minimum is like 8GB and above.
> If guix is the same thing then no problem but for surely it need to be
> mentioned somewhere obvious(i didnt find it anywhere saying that).

The ideal situation is that substitutes for these packages are
available, and you don't have to build them.

Using current Guix master branch, I receive a substitute for
libreoffice. Maybe you just need to update, with `guix pull`?

In general, if you want to compile software, there will be some programs
that require a lot of computer to compile. Not even 10 GB RAM will be
enough in all cases.




  reply	other threads:[~2021-04-13 17:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  5:39 bug#47717: guix outrageously exhaust itself (freeze) when there is package build failure bo0od
2021-04-12 18:04 ` bug#47717: guix becomes unresponsive while building the 'vigra' package Leo Famulari
2021-04-13 11:03   ` bo0od
2021-04-13 17:35     ` Leo Famulari [this message]
2021-04-14 16:06       ` bo0od
2021-04-14  8:21     ` Mark H Weaver
2021-04-14 17:08       ` bo0od
2021-04-12 18:41 ` bug#47717: guix outrageously exhaust itself (freeze) when there is package build failure Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-12 22:59   ` raingloom
2021-04-13 11:34   ` bo0od
2021-04-14  0:40     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-14 16:54       ` bo0od
2021-04-15 19:56         ` Mark H Weaver
2021-04-16  3:08           ` bo0od
2021-04-21  1:35           ` Maxim Cournoyer
2021-04-22 18:34             ` Mark H Weaver
2021-04-25  8:14               ` Efraim Flashner

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=YHXWfNAWojS67oXE@jasmine.lan \
    --to=leo@famulari.name \
    --cc=47717@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    /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).