> On 3 Jun 2026, at 13:46, Sergey Bugaev <[email protected]> wrote:
>
> While you can likely compile simple Mach userland binaries with
> something generic (perhaps even distro-porivded Clang with some
> AArch64 -target), for more serious glibc and Hurd work you want a full
> aarch64-gnu cross-toolchain. Are you familiar with the process for
> setting up such a cross environment, navigating all the circular
> dependencies between mig, gcc, gnumach, glibc, hurd?
I have a few cross toolchains with gcc 15 with libc 2.43, targeting the the 3
arch
of gnumach and they all fully compile hurd. Although I am still playing around
setting a few images or overlays on top of debian/gentoo with the built
kernel/userland
so I can stress test my build environment.
>
>> But I was thinking for now, in a
>> ew days, to raise a couple of pull request to your branch in GitHub repo
>> wip-aarch64
>> branche.
>
> I don't think moving discussions over to Microsoft GitHub is a good
> idea, especially given what they've been up to lately and the
> resulting exodus of high-profile free software projects [0][1][2].
>
> [0]: https://ziglang.org/news/migrating-from-github-to-codeberg/
> [1]: https://mitchellh.com/writing/ghostty-leaving-github
> [2]: https://lucumr.pocoo.org/2026/4/28/before-github/
Seen that.
> Generally, there likely isn't much disagreement on the fact that plain
> text mailing lists are not a very modern or straightforward workflow
> :) I would likely be in favor of moving Hurd development to some
> independent Forgejo instance, for example, if that was on the table.
> But since (until) we haven't done something like that, this list (and
> the IRC channel) is where the development happens, in the open. We
> have a community here; this thread has already attracted the attention
> of Jessica and Luca, beside Samuel and myself whom you explicitly
> cc'ed.
No problems with old tech, not too young myself. It gives me a good
excuse to start using IRC again.
> So I suggest you both host a publicly-accessible Git repo (on GitHub
> or wherever you prefer) with the latest revision of your work, and
> post patches (against the rebased version of my branch) to this list,
> where we will discuss and review it, in public, as a community.
>
>> To add the couple of real bug fixes we found on these patches I sent, and
>> hopefully a PL011 working driver.
>
> Cool, have you made progress on that?
Very little, mostly research. But now that I am happy with the toolchains is my
next focus.
Paulo
