From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Guix build output insufficient
Date: Thu, 13 Sep 2018 09:23:21 +0200
Message-ID: <878t45kgie.fsf@elephly.net>
References: <20180911082653.27gmposcatilbsuq@thebird.nl>
	<875zzcl09b.fsf@elephly.net>
	<20180911162321.077cfefb@scratchpost.org>
	<87r2hzjjgr.fsf@elephly.net>
	<20180912152505.x4gi4wp4jazl2352@thebird.nl>
	<20180913064505.6rhav3mcifcj6tcn@thebird.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53141)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1g0Lyk-0007t6-Up
	for guix-devel@gnu.org; Thu, 13 Sep 2018 03:23:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1g0Lyh-0003Ro-QX
	for guix-devel@gnu.org; Thu, 13 Sep 2018 03:23:54 -0400
Received: from sender-of-o51.zoho.com ([135.84.80.216]:21011)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <rekado@elephly.net>) id 1g0Lyh-0003Q3-Fl
	for guix-devel@gnu.org; Thu, 13 Sep 2018 03:23:51 -0400
In-reply-to: <20180913064505.6rhav3mcifcj6tcn@thebird.nl>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>


Pjotr Prins <pjotr.public12@thebird.nl> writes:

>> So I ran
>>
>>    guix build --log-file /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-dia=
mond-0.9.22.drv
>>
>> which gave me
>>
>>    /var/log/guix/drvs/wk/9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.d=
rv.bz2
>>
>> which contains the build log for this failed build, including the "foo"
>> error message.
>
> Another thing we should capture somewhere is that some build systems
> create full log files. For example cmake creates elaborate output in
>
> CMakeFiles/CMakeError.log
> CMakeFiles/CMakeOutput.log
>
> inside the build directory (guix package -i foo -K)

This is more difficult and I think people should better look at the
build log.  =E2=80=9Cguix package -i foo -K=E2=80=9D is not so common, I th=
ink, because
=E2=80=9Cguix build foo -K=E2=80=9D exists for those cases where you want t=
o debug a
build.

=E2=80=9Cguix package=E2=80=9D is primarily user-facing, whereas =E2=80=9Cg=
uix build=E2=80=9D is for
people packaging things.

--
Ricardo