unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix-devel <guix-devel@gnu.org>
Cc: Mathieu Othacehe <othacehe@gnu.org>
Subject: i586-gnu builds on ci.guix
Date: Sat, 05 Nov 2022 19:23:24 +0100	[thread overview]
Message-ID: <87r0yhi7kz.fsf@gnu.org> (raw)
In-Reply-To: <87leosniim.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 03 Nov 2022 16:51:29 +0100")

Hi!

Ludovic Courtès <ludo@gnu.org> skribis:

>      - i586-gnu: Chris and I fixed core packages (test failures;
>        bordeaux.guix is building them and I’ll enable it on ci.guix real
>        soon now.

I was blissfully optimistic: to do that, we first need to run
‘cuirass-remote-worker’ in the childhurds (which are cross-compiled).

Alas Cuirass depends on Fibers, which is currently Linux-only¹, so we
cannot {cross-,}build it for GNU/Hurd.  The good news is that
‘remote-worker.scm’ itself doesn’t seem to use Fibers.  So I wonder if
we could arrange to build a stripped-down package that contains nothing
but ‘cuirass-remote-worker’.  WDYT?

Cuirass also depends on Avahi, which is currently not buildable for
GNU/Hurd due to libcap requiring on Linux-specific headers, and it seems
to be a hard requirement².  Unfortunately ‘remote-worker.scm’ requires
it.

Thoughts?

Ludo’.

¹ There’s preliminary work to address that:
  <https://github.com/wingo/fibers/pull/53>

² AFAICS Debian doesn’t have it on GNU/Hurd either:
  <https://packages.debian.org/bullseye/libcap2>


  reply	other threads:[~2022-11-05 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 15:51 Release progress, week 4 Ludovic Courtès
2022-11-05 18:23 ` Ludovic Courtès [this message]
2022-11-12 16:49   ` i586-gnu builds on ci.guix Mathieu Othacehe
2022-11-17 14:57     ` 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=87r0yhi7kz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@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).