From: ludo@gnu.org (Ludovic Courtès)
To: mhw@netris.org
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] Add 'file' to %final-inputs; patch /usr/bin/file
Date: Fri, 22 Aug 2014 11:03:48 +0200 [thread overview]
Message-ID: <87siko5217.fsf@gnu.org> (raw)
In-Reply-To: <87iollbzkm.fsf_-_@netris.org> (mhw@netris.org's message of "Thu, 21 Aug 2014 12:02:49 -0400")
mhw@netris.org skribis:
> I chose to add a 'file-boot0' to '%boot0-inputs' to make 'file'
> available as early as possible in the bootstrap, on the theory that any
> library could soon depend on 'file'.
That makes sense.
> I've successfully built 'hello' on i686 with these patches applied, but
> I've not yet tested them on MIPS. If I test them on the Loongson 3A
> machine, then when hydra offloads the same builds, the build logs on
> hydra will be empty. It would be good if hydra would copy over the
> saved build log in that case.
Yes, that’s annoying. The crux of the problem is that the offload hook
just invokes ‘guix build’ on the remote machine, and ‘guix build’
produces no output when the thing is already built.
We could add a ‘--replay-log’ option to ‘guix build’ to handle that
case.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2014-08-22 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 18:58 Making 'file' an implicit native input in core-updates mhw
2014-08-20 19:21 ` Eric Bavier
2014-08-20 21:33 ` Ludovic Courtès
2014-08-21 16:02 ` [PATCHES] Add 'file' to %final-inputs; patch /usr/bin/file mhw
2014-08-22 6:12 ` mhw
2014-08-22 9:09 ` Ludovic Courtès
2014-08-22 9:03 ` Ludovic Courtès [this message]
2014-08-30 20:22 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87siko5217.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).