From: Joshua Branson via Guix-patches via <guix-patches@gnu.org>
To: zamfofex <zamfofex@twdb.moe>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, 51770@debbugs.gnu.org
Subject: [bug#51770] progress report on updating the Hurd packages
Date: Fri, 24 Feb 2023 07:57:38 -0500 [thread overview]
Message-ID: <87pm9z8blp.fsf@dismail.de> (raw)
In-Reply-To: <966142788.351797.1677149996665@privateemail.com> (zamfofex@twdb.moe's message of "Thu, 23 Feb 2023 07:59:56 -0300 (BRT)")
zamfofex <zamfofex@twdb.moe> writes:
> Hello, everyone! I just wanted to be able to report my progress with updating the Hurd packages.
>
> I have been able to get past my previous issues with building GMP, I think, but
> it seems that the glibc in Guix is still too outdated for the whole endeavor to
> succeed.
>
> I could either update the glibc package again or simply apply a patch to it
> (since the change needed seems to be small enough), but that would take quite a
> while waiting for things to build, and I’m not sure I’m up for it at the moment.
>
> I plan to pick this effort back up again at some point, but at the moment I’m a
> bit tired of having to wait for packages to build for multiple days. But if
> anyone wants to pick up where I left off, I will upload a ‘git diff’ with my
> current changes. (Applicable to ‘core-updates’.)
>
> Here is some more insight based on my conversations on #hurd:
>
> - https://logs.guix.gnu.org/hurd/2023-02-20.log
> - https://logs.guix.gnu.org/hurd/2023-02-21.log
>
> If anyone wants to take this work meanwhile, please do let me know somehow so that we don’t end up duplicating effort!
>
> Thanks for everyone’s amazing work on the Hurd and on Guix!
Here is an email that was send in the bug-hurd archives recently that
talked about how to build the Hurd on GNU/Linux. Hopefully this will
help others to update our Hurd packages:
https://lists.gnu.org/archive/html/bug-hurd/2023-01/msg00132.html
Here are some scripts that automate this process:
https://github.com/flavioc/cross-hurd
The hurd was a wiki page for this as well (probably outdated):
https://darnassus.sceen.net/~hurd-web/toolchain/cross-gnu/
Also for those of you who don't know, the Hurd is getting a ton of
developer attention right now. Work in progress includes SMP work, 64
bit kernel (with 32 bit address space), some re-using netBSD's driver's
work, etc. Now's a great time get subscribed to the Hurd's mail
developmental email list: bug-hurd:
https://lists.gnu.org/mailman/listinfo/bug-hurd
prev parent reply other threads:[~2023-02-24 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 10:59 progress report on updating the Hurd packages zamfofex
2023-02-24 12:57 ` Joshua Branson via Guix-patches via [this message]
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=87pm9z8blp.fsf@dismail.de \
--to=guix-patches@gnu.org \
--cc=51770@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.de \
--cc=zamfofex@twdb.moe \
/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).