unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Paul Dufresne <dufresnep@gmail.com>
To: help-guix@gnu.org
Subject: How/When will guix pull stop to compile the 616 files?
Date: Mon, 7 Aug 2017 20:59:18 -0400	[thread overview]
Message-ID: <CAGQ-=q1aVg6rmUHQMQYyczpFpF_-r76z76u+kRMZOedg_p4yqw@mail.gmail.com> (raw)

I have seen it too many times already.

The first times, it was stopping because my machine hangs in the
desktop environment
if I let it without inputing stuff once in a while. My machine have
broken ACPI tables...
not your fault I suppose...

Next, after I learns to start it in tty terminal (Ctrl-Alt 2), it had
stopped at 96% because
of gc out of memory. I learn that 2 GB of memory was just too small
and had to activate
my swap partition for it to finished.

Oh, I also forgot that I learned to add the 2 exports line in my
.bashrc file because without
it it would complain guile-git is not installed, even if it is.

Well, I thought after first success, it would stop to compile it ...
but it seems to compile
it every time... or maybe if one of the 616 files changed, it have to
recompile them all?

I wonder, why it cannot recompile only the files that have changed.

             reply	other threads:[~2017-08-08  0:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  0:59 Paul Dufresne [this message]
2017-08-08  1:43 ` How/When will guix pull stop to compile the 616 files? Paul Dufresne
2017-08-08  7:50   ` Alex Sassmannshausen
2017-08-08 13:02     ` Paul Dufresne
2017-08-08 20:23       ` Ricardo Wurmus
2017-08-08 20:39         ` Jack Hill
2017-08-09  5:43           ` Paul Dufresne
2017-08-09  8:08           ` Ricardo Wurmus
2017-08-09 13:41             ` Jack Hill
2017-08-13  3:21       ` Quiliro Ordonez Baca

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='CAGQ-=q1aVg6rmUHQMQYyczpFpF_-r76z76u+kRMZOedg_p4yqw@mail.gmail.com' \
    --to=dufresnep@gmail.com \
    --cc=help-guix@gnu.org \
    /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.
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).