unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 40006@debbugs.gnu.org
Subject: bug#40006: [core-updates] Merge wip-hurd
Date: Tue, 10 Mar 2020 09:48:05 +0100	[thread overview]
Message-ID: <87h7yw4muy.fsf@gnu.org> (raw)

Hello Guix'y supporters of the Hurd,

This is a follow-up to a discussion on guix-devel
https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00081.html to
keep track of merging recent work for the Hurd by Efraim and others
that started on the Guix Days @fosdem20

    https://gitlab.com/Efraim/guix  @wip-hurd-bootstrap

The `wip-hurd' branch @savannah has now been reset* and now contains a
set of patches that allow for Hurd development, either by building
packages natively or by cross-building.

Most interesting here are the hurd bootstrap binaries and patches to get
through "commencement".  Efraim built a first set of bootstrap binaries
but I found we at least need some minimal set of glibc patches

    glibc-hurd-clock_t_centiseconds.patch
    glibc-hurd-clock_gettime_monotonic.patch
    glibc-hurd-signal-sa-siginfo.patch

which I added and so I built a new set.  While this mostly works, we may
want to look at/include more patches from the Debian glibc delta

    https://salsa.debian.org/glibc-team/glibc/-/tree/glibc-2.31/debian/patches/hurd-i386

...but how to choose?

This patch series may be especially interesting as I have been also
using a number of hacks to get to build `hello' natively, avoiding
failing/hanging tests here and there

    HACK gnu: acl: Add patches for the Hurd, disable tests.
    HACK gnu: gettext-minimal: Expect test-raise test to fail on the Hurd.
    HACK gnu: check: Skip hanging tests on the Hurd.
    HACK gnu: guile: Disable tests on Hurd.
    HACK gnu: coreutils: Disable tests on Hurd.

I haven't re-evaluated the need for these yet after my last glibc
patches and I haven't included these on the wip-hurd branch; these live
on wip-hurd-system on my gitlab

    https://gitlab.com/janneke/guix  @wip-hurd-system

That's also where my scratchbook on the Hurd lives

   https://gitlab.com/janneke/guix/-/blob/wip-hurd-system/THE-HURD

As discussed on guix-devel, we need to build gnumach-headers and
hurd-headers from a tarball release.  Initially I tried the latest
official releases but they are too old.  So I have created unofficial
source tarballs for Gnumach and Hurd tarball by running `make dist' on
the a git checkout on the Debian Hurd and uploaded them here

    http://lilypond.org/janneke/hurd

wip-hurd is branched off core-updates about two weeks ago; I will now
start with rebasing and re-evaluating on latest core-updates.

Greetings,
janneke

*) Everything from Manolis' old wip-hurd since been merged or ported to
   the new wip-hurd.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

             reply	other threads:[~2020-03-10  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  8:48 Jan Nieuwenhuizen [this message]
2020-03-10  8:54 ` bug#40006: [core-updates] Merge wip-hurd Manolis Ragkousis
2020-03-26 12:25 ` Jan Nieuwenhuizen
2020-03-26 12:51   ` Efraim Flashner
2020-03-26 14:08     ` Jan Nieuwenhuizen
2020-03-26 14:26   ` 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=87h7yw4muy.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=40006@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 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).