From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Error messages and progress report Date: Sun, 09 Dec 2012 21:50:38 +0100 Message-ID: <87ehizc5lt.fsf@gnu.org> References: <201212092101.21170.andreas@enge.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33573) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Thnph-0001sK-Kx for bug-guix@gnu.org; Sun, 09 Dec 2012 15:50:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Thnpg-00031V-KE for bug-guix@gnu.org; Sun, 09 Dec 2012 15:50:41 -0500 Received: from mail4-relais-sop.national.inria.fr ([192.134.164.105]:64191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Thnpg-00031M-DT for bug-guix@gnu.org; Sun, 09 Dec 2012 15:50:40 -0500 In-Reply-To: <201212092101.21170.andreas@enge.fr> (Andreas Enge's message of "Sun, 9 Dec 2012 21:01:21 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Andreas Enge Cc: bug-guix@gnu.org Hi, Andreas Enge 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 # #vu8(8 0 0 0 0 0 0 0)=20 > ...] > > ERROR: In procedure put-bytevector: > ERROR: In procedure fport_write: Bad file descriptor Weird. Here=E2=80=99s it=E2=80=99s trying to write to the socket correspon= ding to an open connection to the daemon. We=E2=80=99d need to look at the output of =E2=80=98strace=E2=80=99 to see what happened to this file descriptor. Can= you try that, if that=E2=80=99s 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: . > Concerning the downloads, would it be possible to easily add a progress > bar? In particular since the first download was gcc, quite some time pass= ed > 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=E2=80=99.