unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: George Clemmer <myglc2@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: help-guix@gnu.org
Subject: Re: *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS ***
Date: Wed, 31 Oct 2018 20:09:15 -0400	[thread overview]
Message-ID: <cuczhut3bh0.fsf@gmail.com> (raw)
In-Reply-To: <cuc1s854qlr.fsf@gmail.com>


George Clemmer <myglc2@gmail.com> writes:

> Hi Mark,
>
> Mark H Weaver <mhw@netris.org> writes:
>
>> George Clemmer <myglc2@gmail.com> writes:
>>> Brian, I believe that what you are experiencing as a "hang" is actually
>>> the incredibly long time that it takes for guile to bootstrap itself.
>>
>> That's not what's happening here, because this hang is happening during
>> "make check".  Thanks anyway :)
>>
>>        Mark
>
> Well, ISTM 'make check-TESTS' is bootstrapping guile for some reason. I
> say that because the fragment quoted by Brian ...
>
>> This is what is displaced on the screen when the hang occurs:
>>
>> …
>> make  check-TESTS
>> make[3]: Entering directory ‘/tmp/guix-build-guile-2.2.3.drv-0/guile-2.2.3’
>> Testing /tmp/guix-build-guile-2.2.3.drv-0/guile-2.2.3/meta/guile …
>> with GUILE_LOAD_PATH=/tmp/guix-guild-guile-2.2.3.drv-0/guile-2.2.3/test-suite
>
> ... matches the log for ...
>
> building /gnu/store/55f2ihxyjyskpv9w0m2c4g0zcinjylif-guile-2.2.3.drv...
>
> ... that I have here.
>
> HTH - George

And, with the current state of the guix infrastructure, even a 'guix
pull' on a fresh vm-image triggers guile bootstrap. And a guile
bootstrap, on the best of days, displays these symptoms: howling CPUs
and hardly any disk activity.

So, relative to what one expects when installing a distro this feels
hung. Not the most confidence inspiring experience to subject a guix
noob to ;-)

  reply	other threads:[~2018-11-01  0:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 15:42 *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS *** Brian Woodcox
2018-10-31 17:41 ` Leo Famulari
2018-10-31 18:23   ` Brian Woodcox
2018-10-31 18:35 ` Mark H Weaver
2018-10-31 18:47   ` Brian Woodcox
2018-11-01  7:35     ` Mark H Weaver
2018-10-31 20:50   ` Brian Woodcox
2018-10-31 21:54     ` George Clemmer
2018-10-31 22:30       ` Brian Woodcox
2018-10-31 23:44         ` George Clemmer
2018-11-01  2:33           ` Mark H Weaver
2018-11-01  3:35             ` George Clemmer
2018-10-31 22:47       ` Mark H Weaver
2018-10-31 23:57         ` George Clemmer
2018-11-01  0:09           ` George Clemmer [this message]
2018-11-06 15:27             ` swedebugia
2018-11-06 18:24               ` George Clemmer
2018-11-07 11:40                 ` swedebugia
2018-11-07 13:01                   ` George Clemmer
2018-11-07 15:16         ` Christopher Lemmer Webber
2018-11-01  1:35     ` Mark H Weaver
2018-11-01  2:58       ` Brian Woodcox
2018-11-06  5:14       ` Mark H Weaver
2018-11-06 17:08         ` Brian Woodcox
2018-11-06 23:22           ` Brian Woodcox

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=cuczhut3bh0.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mhw@netris.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).