unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Getting the Guix Build Coordinator agent working on the Hurd
Date: Tue, 16 Feb 2021 08:57:31 +0000	[thread overview]
Message-ID: <87im6sfkzo.fsf@cbaines.net> (raw)
In-Reply-To: <87tuqekheb.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]


Christopher Baines <mail@cbaines.net> writes:

> This has been on my todo list ever since the childhurd service came in
> to existence. I spent some more time looking at it yesterday, and did
> manage to get the agent working in a childhurd VM, at least somewhat.
>
> Firstly, guile-lib needed tweaking so that it actually cross compiles,
> I've sent a patch [1].
>
> 1: https://lists.gnu.org/archive/html/guile-devel/2021-02/msg00004.html
>
> Adding the agent service also required this tweak [2].
>
> 2: https://issues.guix.gnu.org/46506
>
> Then I faced two problems with the guix-build-coordinator
> package. Firstly, wrap-program picks bash for Linux for the wrapper
> script, which isn't very useful. I hacked around this by setting the
> PATH such that it picked bash for the Hurd. In terms of properly fixing
> this, I guess that needs to somehow be able to find the right bash, I'm
> not sure how though?
>
> The second issue is that I'm not sure capturing the build time
> GUILE_LOAD_COMPILED_PATH doesn't seem to work, at least file says that
> the .go files this contains are built for a 64-bit architecture. I
> worked around this by constructing the GUILE_LOAD_COMPILED_PATH from the
> inputs I knew should be on it. Maybe it should always have been done
> this way, any ideas?

The above patches, hacks and questions are still relevant, but I've made
some progress on the issue below.

> There's also one problem probably within the Guix Build Coordinator
> itself, after doing a few builds, it will just stop. I've only seen this
> behaviour on the Hurd, but I'm unsure how to debug it, any suggestions?
> My only idea is add more logging.

I tried disabling a few of the optional features plus unnecessary locks
on the hurd [1], and with those changes I no longer see it just stop,
which is great, as then builds just keep happening :)

1: https://git.cbaines.net/guix/build-coordinator/commit/guix-build-coordinator?id=b3733bca21de607fd7a70319e66e3ff49996a974

For the guix.cbaines.net build farm, I've now got an additional machine
running two childhurd VM's, and I plan to scale this up to 7 or 8 in the
coming days to see how far it's possible to get building things for the
i586-gnu.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2021-02-16  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 11:39 Getting the Guix Build Coordinator agent working on the Hurd Christopher Baines
2021-02-15 15:12 ` Joshua Branson
2021-02-16  8:58   ` Christopher Baines
2021-02-16  8:57 ` Christopher Baines [this message]
2021-02-18  9:25   ` Christopher Baines
2021-02-18 17:35 ` Ludovic Courtès
2021-02-23 20:58   ` Christopher Baines
2021-03-10 10:10     ` 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=87im6sfkzo.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --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 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).