all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: guix-devel@gnu.org
Subject: Re: What's needed to get things building for i586-gnu (the hurd) post core-updates?
Date: Fri, 05 May 2023 15:59:45 +0100	[thread overview]
Message-ID: <87354a3jrs.fsf@cbaines.net> (raw)
In-Reply-To: <87o7myc0cy.fsf@jpoiret.xyz>

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


Josselin Poiret <dev@jpoiret.xyz> writes:

> Christopher Baines <mail@cbaines.net> writes:
>> 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.
>
> Just to recap, as you mentioned on IRC, the coreutils configure phase
> seems to miss hurd.h, even though it is included in the bootstrap glibc.
> It might be due to the coreutils upgrade, since I don't see what else
> could've changed this derivation.  I don't have a childhurd at the
> moment (because a cross-compiled Hurd fails to run), so I can't really
> test native compilation as above :(

I think the first bit to look at here is not that coreutils-boot0 is
failing, but why it's started being used, because I'm not even sure
about that.

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

  reply	other threads:[~2023-05-05 15:01 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 [this message]
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
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=87354a3jrs.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=dev@jpoiret.xyz \
    --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 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.