From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Error messages and progress report
Date: Sun, 09 Dec 2012 21:50:38 +0100 [thread overview]
Message-ID: <87ehizc5lt.fsf@gnu.org> (raw)
In-Reply-To: <201212092101.21170.andreas@enge.fr> (Andreas Enge's message of "Sun, 9 Dec 2012 21:01:21 +0100")
Hi,
Andreas Enge <andreas@enge.fr> skribis:
> $ guix-package -n -i hello
[...]
> In guix/store.scm:
> 408: 1 [add-text-to-store # "libsigsegv-2.10.tar.gz-guile-builder" ...]
> In unknown file:
> ?: 0 [put-bytevector #<input-output: socket 5> #vu8(8 0 0 0 0 0 0 0)
> ...]
>
> ERROR: In procedure put-bytevector:
> ERROR: In procedure fport_write: Bad file descriptor
Weird. Here’s it’s trying to write to the socket corresponding to an
open connection to the daemon. We’d need to look at the output of
‘strace’ to see what happened to this file descriptor. Can you try
that, if that’s easily reproducible?
> After that, things seem to proceed well for the moment;
> $ guix-package -i hello
> starts by downloading things and compiling them.
Note that you can get pre-built binaries for x86_64-linux from
hydra.nixos.org:
<http://lists.gnu.org/archive/html/bug-guix/2012-11/msg00042.html>.
> Concerning the downloads, would it be possible to easily add a progress
> bar? In particular since the first download was gcc, quite some time passed
> without any hint as to whether the program was still working.
Yes, I agree this would be nice. It can be achieved by tweaking
guix/build/download.scm and related code.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-12-09 20:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 20:01 Error messages and progress report Andreas Enge
2012-12-09 20:50 ` Ludovic Courtès [this message]
2012-12-10 9:19 ` Andreas Enge
2012-12-10 13:26 ` Ludovic Courtès
2012-12-10 18:17 ` Andreas Enge
2012-12-10 21:29 ` Ludovic Courtès
2012-12-10 22:12 ` Andreas Enge
2012-12-10 22:59 ` Ludovic Courtès
2012-12-10 23:22 ` Andreas Enge
2012-12-11 12:22 ` Andreas Enge
2012-12-11 13:20 ` Nikita Karetnikov
2012-12-11 14:37 ` Ludovic Courtès
2012-12-11 15:40 ` Andreas Enge
2012-12-11 21:15 ` Andreas Enge
2012-12-11 23:16 ` Ludovic Courtès
2012-12-12 8:55 ` Andreas Enge
2012-12-13 19:17 ` Andreas Enge
2012-12-11 23:15 ` Ludovic Courtès
2012-12-12 8:48 ` Andreas Enge
2012-12-12 13:14 ` Ludovic Courtès
2013-01-06 17:49 ` Ludovic Courtès
2013-01-10 9:56 ` Andreas Enge
2013-01-10 10:45 ` Andreas Enge
2013-01-10 21:14 ` Ludovic Courtès
2013-01-11 13:49 ` Andreas Enge
2013-01-11 14:58 ` 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=87ehizc5lt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-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.
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).