From: jbranso@dismail.de
To: "Christopher Baines" <mail@cbaines.net>,
"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 19:02:53 +0000 [thread overview]
Message-ID: <0e53cab97ee5496ed0aa48f94faea644@dismail.de> (raw)
In-Reply-To: <87354a3jrs.fsf@cbaines.net>
May 5, 2023 11:02 AM, "Christopher Baines" <mail@cbaines.net> wrote:
> 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.
Fun fact of the day, the Debian GNU/Hurd is starting to build 64-bit
packages:
https://lists.gnu.org/archive/html/bug-hurd/2023-05/msg00073.html
next prev parent reply other threads:[~2023-05-05 19:03 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 [this message]
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
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=0e53cab97ee5496ed0aa48f94faea644@dismail.de \
--to=jbranso@dismail.de \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@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 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).