From: Catonano <catonano@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: how to get the path of the logfile after an unsuccesful build?
Date: Sun, 11 Mar 2018 07:46:52 +0100 [thread overview]
Message-ID: <CAJ98PDxmiSBLEcgd75RY54R-JrrORg2_NAENhVCY8-JbXjp_GA@mail.gmail.com> (raw)
In-Reply-To: <CAJ98PDywPY+wRBFiFZPtBSgokDJJht12U8Q+p+xy7SzuznhSnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
2018-03-11 7:28 GMT+01:00 Catonano <catonano@gmail.com>:
>
>
> 2018-03-09 10:15 GMT+01:00 ng0 <ng0@n0.is>:
>
>> Hi,
>>
>> did we ever talk about that there's too little information on how to get
>> the current log file of a failed build? I need this right now (the full
>> log)
>> and I can't remember how, and making use of the log folder in
>> var/log/guix/ won't
>> help either.
>
>
> last time I needed to see a build log, I think it was the "-K" option
> passed to guix build
>
> If the build fails, you'll see a line at the end, in the terminal,
> reminding you that the build log is reachable at a certain location
>
>
>
Look, there's a manual page about that !
https://www.gnu.org/software/guix/manual/html_node/Debugging-Build-Failures.html#Debugging-Build-Failures
Are we talking about the same thing ?
[-- Attachment #2: Type: text/html, Size: 1671 bytes --]
next prev parent reply other threads:[~2018-03-11 6:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 9:15 how to get the path of the logfile after an unsuccesful build? ng0
2018-03-09 13:52 ` Ricardo Wurmus
2018-03-09 14:06 ` ng0
2018-03-09 14:28 ` Clément Lassieur
2018-03-09 14:39 ` ng0
2018-03-09 14:44 ` Hartmut Goebel
2018-03-09 14:49 ` ng0
2018-03-09 15:28 ` Clément Lassieur
2018-03-10 15:31 ` Ludovic Courtès
2018-03-10 22:29 ` Ricardo Wurmus
2018-03-09 21:49 ` Mark H Weaver
2018-03-12 0:55 ` Mark H Weaver
2018-03-23 4:54 ` Chris Marusich
2018-03-11 6:28 ` Catonano
2018-03-11 6:46 ` Catonano [this message]
2018-03-11 11:12 ` Ricardo Wurmus
2018-03-11 8:11 ` ng0
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=CAJ98PDxmiSBLEcgd75RY54R-JrrORg2_NAENhVCY8-JbXjp_GA@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guix-devel@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 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.