What's needed to get things building for i586-gnu (the hurd) post core-updates?

[Christopher Baines <mail@cbaines.net>]

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

Hey!

I've been watching the substitute availability numbers recover after the
core-updates merge, but one system where there hasn't been any movement
is i586-gnu. Prior to the merge there were some things building at least
(17% substitute availability [1]), but now no packages seem to build.

1: https://data.guix.gnu.org/revision/472706ae2f9160833951a4e4bcc4c206e03097b0/package-substitute-availability

I've fixed the #<gexp ... in builder script problem for gcc-cross-boot0,
but then I've got a bit stuck on what the remaining issues are.

I think the use of coreutils-boot0 in the source for gcc-boot0 is a
problematic change introduced in core-updates [2], at least
coreutils-boot0 fails to build.

2: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/commencement.scm?id=6922069bcbe5c08da09c00e5aad44e390ebd1cc7#n2328

I've also seen a few test failures in early derivations, I think
findutils-boot0 is among them [3].

3: https://data.guix.gnu.org/gnu/store/rbgsr6dywmcrrd7baymjskfxw5sh08nz-findutils-boot0-4.9.0.drv

You can ask the data service what the blocking builds are for the hurd
[4], which currently reports coreutils-boot0 (which I think is being
pulled in for the gcc-cross-boot0 source as I describe above), and
findutils-boot0 which has the test failures.

4: https://data.guix.gnu.org/revision/3efdc84bbd1819aeef6e2290aaf54bc88ba72dda/blocking-builds?system=i586-gnu&target=none&limit_results=50

Any ideas?

Thanks,

Chris

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