June 3, 2026 at 8:46 AM, "Sergey Bugaev" <[email protected] 
mailto:[email protected]?to=%22Sergey%20Bugaev%22%20%3Cbugaevc%40gmail.com%3E > 
wrote:



> 
> On Wed, Jun 3, 2026 at 1:22 PM Paulo Duarte <[email protected]> wrote:
> 
> > 
> > Sergey,
> > 
> Hello,
> 
> > 
> > I went a bit silent as I am finishing up setting a sane cross compilation 
> > environment that
> >  will allow me to continue my experiments in a better way.
> > 
> How much have you been able to achieve / figure out here? Do you need
> help/guidance?
> 
> 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?
> 
> > 
> > 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/
> 
> 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.

sourcehut may be another option as well.  It's only $48 / year or so.
I currently have an account there, so I'd be happy to mirror the hurd 
git accounts there, if there's interest in trying out sourcehut.

https://sourcehut.org/

> 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?
> 
> Sergey
>

Reply via email to