From: Ricardo Wurmus <rekado@elephly.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix build output insufficient
Date: Thu, 13 Sep 2018 09:23:21 +0200 [thread overview]
Message-ID: <878t45kgie.fsf@elephly.net> (raw)
In-Reply-To: <20180913064505.6rhav3mcifcj6tcn@thebird.nl>
Pjotr Prins <pjotr.public12@thebird.nl> writes:
>> So I ran
>>
>> guix build --log-file /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv
>>
>> which gave me
>>
>> /var/log/guix/drvs/wk/9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv.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. “guix package -i foo -K” is not so common, I think, because
“guix build foo -K” exists for those cases where you want to debug a
build.
“guix package” is primarily user-facing, whereas “guix build” is for
people packaging things.
--
Ricardo
next prev parent reply other threads:[~2018-09-13 7:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:26 Guix build output insufficient Pjotr Prins
2018-09-11 9:04 ` Pjotr Prins
2018-09-11 9:55 ` Danny Milosavljevic
2018-09-11 10:41 ` Pierre Neidhardt
2018-09-11 11:59 ` Devan Carpenter
2018-09-11 11:52 ` Ricardo Wurmus
2018-09-11 14:23 ` Danny Milosavljevic
2018-09-12 6:52 ` Ricardo Wurmus
2018-09-12 15:25 ` Pjotr Prins
2018-09-13 6:45 ` Pjotr Prins
2018-09-13 7:23 ` Ricardo Wurmus [this message]
2018-09-12 17:09 ` Ludovic Courtès
2018-09-12 17:25 ` Ricardo Wurmus
2018-09-12 17:34 ` Tobias Geerinckx-Rice
2018-09-12 17:42 ` Tobias Geerinckx-Rice
2018-09-12 17:52 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t45kgie.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.