From: raingloom <raingloom@riseup.net>
To: 48024@debbugs.gnu.org
Subject: bug#48024: glib-2.62.6 build fails i686
Date: Mon, 26 Apr 2021 17:26:52 +0200 [thread overview]
Message-ID: <20210426172652.005ae12b@riseup.net> (raw)
In-Reply-To: <874kftd8fl.fsf@disroot.org>
On Sun, 25 Apr 2021 23:35:42 -0400
Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> At the end of the build log this log is mentioned
> `/tmp/guix-build-glib-2.62.6.drv-0/build/meson-logs/testlog.txt`
> but it does not exist.
>
Use the --keep-failed build option, otherwise the /tmp/guix-build-*
directories are deleted when their respective builds fail. Otherwise
they would just waste space.
next prev parent reply other threads:[~2021-04-26 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 3:35 bug#48024: glib-2.62.6 build fails i686 Bone Baboon via Bug reports for GNU Guix
2021-04-26 15:26 ` raingloom [this message]
2021-04-27 19:25 ` Bone Baboon via Bug reports for GNU Guix
2021-04-28 3:23 ` Mark H Weaver
2021-05-03 22:00 ` Bone Baboon via Bug reports for GNU Guix
2021-05-04 0:38 ` Leo Famulari
2021-05-04 3:01 ` Mark H Weaver
2021-05-04 6:18 ` Efraim Flashner
2021-05-04 20:01 ` Mark H Weaver
2021-05-04 20:08 ` Mark H Weaver
2021-05-04 22:52 ` Bone Baboon via Bug reports for GNU Guix
2021-05-05 8:38 ` Efraim Flashner
2021-05-05 21:15 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 0:20 ` Mark H Weaver
2021-05-06 0:35 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 6:45 ` Efraim Flashner
2021-05-06 9:06 ` Bengt Richter
2021-05-06 17:44 ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 17:46 ` Mark H Weaver
2021-05-08 13:26 ` Bengt Richter
2022-03-18 2:26 ` Maxim Cournoyer
2021-05-04 3:56 ` Mark H Weaver
2021-05-05 16:34 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 8:46 ` Mark H Weaver
2021-05-06 19:36 ` Bone Baboon via Bug reports for GNU Guix
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=20210426172652.005ae12b@riseup.net \
--to=raingloom@riseup.net \
--cc=48024@debbugs.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.