Re: [RFC PATCH 00/23] aarch64-gnu port

[Joseph Myers <jsm@polyomino.org.uk>]

On Wed, 3 Jan 2024, Sergey Bugaev wrote:

> To build this, you need an aarch64-gnu toolchain (binutils, GCC, MIG),
> and GNU Mach headers for AArch64. I have posted the patches for
> binutils, GCC, and GNU Mach to the bug-hurd mailing list; no patches
> are required to build aarch64-gnu-mig.

> There is no AArch64 port of GNU Mach yet; I'm trying to get the ball
> rolling by making this port of glibc. I have only added some AArch64

I think the same principle applies for ports to new (architecture, Hurd) 
pairs as for new (architecture, Linux) pairs: the relevant code needs to 
be in upstream mainline of all components on which glibc build-depends 
before the port can go into glibc (and thus before the symbol versions for 
the port can be determined) - and at the point where it's ready to go in, 
a corresponding build-many-glibcs.py entry should be added as part of the 
patch series.  Parts of <https://sourceware.org/glibc/wiki/NewPorts> may 
be applicable, though that's more oriented to the case where the 
architecture support itself is entirely new.

You can of course do refactors of existing files not specific to 
aarch64-gnu, in preparation for the port, before then, to reduce the size 
of the eventual patch series proposing adding the port to glibc.

-- 
Joseph S. Myers
jsm@polyomino.org.uk