unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 36806@debbugs.gnu.org
Subject: bug#36806: guix package -i guile-emacs takes Build too slow
Date: Thu, 25 Jul 2019 14:53:19 +0200	[thread overview]
Message-ID: <874l3a9sxs.fsf@elephly.net> (raw)
In-Reply-To: <CAEtmmexPr68X2J4omVaRtvAzyMuYMBozf-1X4wTFJUSNGHjQgg@mail.gmail.com>


Rostislav Svoboda <rostislav.svoboda@gmail.com> writes:

> Hi, I'm trying to install guile-emacs using:
>     guix package -i guile-emacs
> It's been running for almost 20 hours, most of the time at the step:
>     building /gnu/store/h8n0z0ihpykz076paavfcp4ply3qx6q0-guile-emacs-0.0.0-0.41120e0.drv...
>     \ 'build' phase
> Is it hanging or not? If not:
> - is there a way to show some progress bar?

Yes, you can pass “--verbosity=2” to see details.

> - 20+ hours isn't it a bit too long anyway?

We have little to no control over build times.  When a package is slow
to be compiled (such as a full bootstrap build of Guile) then it’s going
to take a long time.

I think, though, that Guile Emacs cannot actually be built at all, so
I’m expecting your 20+ hour build to eventually fail.  That’s why Guix
tries to build it locally in the first place instead of downloading a
ready-made binary from our build farm — because the build farm doesn’t
have a binary to offer (because it failed to build it).

This is the view from our build farm:

    https://ci.guix.gnu.org/search?query=guile-emacs+spec%3Aguix-master+system%3Ax86_64-linux

Doesn’t look good.

-- 
Ricardo






  reply	other threads:[~2019-07-25 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  8:54 bug#36806: guix package -i guile-emacs takes Build too slow Rostislav Svoboda
2019-07-25 12:53 ` Ricardo Wurmus [this message]
2019-07-25 13:11   ` Rostislav Svoboda

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874l3a9sxs.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=36806@debbugs.gnu.org \
    --cc=rostislav.svoboda@gmail.com \
    /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).