From: Efraim Flashner <efraim@flashner.co.il>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <mail@cbaines.net>,
guix-devel@gnu.org
Subject: Re: What's needed to get things building for i586-gnu (the hurd) post core-updates?
Date: Sun, 14 May 2023 21:51:14 +0300 [thread overview]
Message-ID: <ZGEtot4AtSMYxQFW@3900XT> (raw)
In-Reply-To: <87pm72aown.fsf@jpoiret.xyz>
[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]
On Sun, May 14, 2023 at 05:55:20PM +0200, Josselin Poiret wrote:
> Hi Ludo and Chris,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
> > Hello!
> >
> > Probably the main issue is that childhurds now fail to boot:
> >
> > https://issues.guix.gnu.org/62307#23
> >
> > We can still build “new” i586-gnu binaries on an “old” childhurd, of
> > course, but to me that’s doing that is less of a priority.
>
> [1] should fix this. We have at least three important failures
> regarding native compilation now:
>
> - coreutils doesn't build. This is because our bootstrap glibc doesn't
> contain all the kernel headers, and coreutils tries to use some of
> them directly. This should be fixable by adding an additional
> bootstrap input for the Hurd with the missing kernel sources, I'm
> trying to get one right now.
>
> While discussing with janneke, we also figured out that
> coreutils-boot0 was probably unneeded as it's only used to rm a file
> in an origin later on that could be removed with pure Guile. That
> would be a world rebuild though so let's leave that for later.
If all you need is to remove coreutils-boot0 from the origin then you
could create a similar boot0 package specifically for the hurd and make
the fix there, and then use the current package or your new one as an
input in later packages based on the architecture.
> - m4 and findutils both have some failing tests, and they seem to be
> crashing. I haven't investigated this yet.
>
> [1] https://issues.guix.gnu.org/63501
>
> --
> Josselin Poiret
--
Efraim Flashner <efraim@flashner.co.il> פלשנר אפרים
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-14 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 14:09 What's needed to get things building for i586-gnu (the hurd) post core-updates? Christopher Baines
2023-05-05 14:35 ` Josselin Poiret
2023-05-05 14:59 ` Christopher Baines
2023-05-05 19:02 ` jbranso
2023-05-06 13:46 ` Christopher Baines
2023-05-07 11:22 ` Christopher Baines
2023-05-07 21:31 ` Ludovic Courtès
2023-05-14 15:55 ` Josselin Poiret
2023-05-14 18:51 ` Efraim Flashner [this message]
2023-05-15 16:46 ` Josselin Poiret
2023-05-15 17:11 ` Efraim Flashner
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=ZGEtot4AtSMYxQFW@3900XT \
--to=efraim@flashner.co.il \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
/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.