From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Re: What's needed to get things building for i586-gnu (the hurd) post core-updates?
Date: Sun, 07 May 2023 12:22:03 +0100 [thread overview]
Message-ID: <87zg6gz8g0.fsf@cbaines.net> (raw)
In-Reply-To: <87h6sp1s7d.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> [[PGP Signed Part:Undecided]]
>
> Christopher Baines <mail@cbaines.net> writes:
>
>> 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.
>
> So, when I say "fixed" here, all I managed to do is stop a gexp ending
> up in the builder script of gcc-boot0. I managed to fix some of the
> problems with the changes I made, but then I tried cross building from
> x86_64-linux, up popped a package which failed to build because it was
> missing the patch. This is relevant as it blocks machines using
> childhurds from reconfiguring past the latest core-updates merge.
>
> While it caused problems, using gexps at least avoided the problem where
> you need to have the patch in the native-inputs as well, so to continue
> going round in circles, that's maybe the direction to now go. As the
> next step though before using gexps in gcc-11, any packages inheriting
> from gcc-11 need to be changed to use gexps for the phases.
>
> I've attempted to do that in #63329 [1], I'll wait to see what the data
> service makes of the changes to see how successful I've been at avoiding
> rebuilds.
>
> 1: https://issues.guix.gnu.org/63329
I've merged #63329 now, and also reverted to the gexp based patching in
gcc-11.
The childhurd system test builds for me at least, although it seems to
fail when run.
Native building for i586-gnu seems to have multiple problems, although I
think the gcc-cross-boot0 source issue is the one that seems hardest to
work around to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-05-07 11:29 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 [this message]
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=87zg6gz8g0.fsf@cbaines.net \
--to=mail@cbaines.net \
--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.