* Joseph Myers:
> 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
On Mon, Mar 11, 2024 at 4:48 PM H.J. Lu wrote:
> I think hurd maintainers can approve and check in all hurd specific
> changes now even if they won't build. The generic changes should
> be looked at more closely so that they have no impacts on any
> future Linux changes and future Linux changes
> On Jan 3, 2024, at 21:14, Sergey Bugaev wrote:
>
> Hello!
>
> This is my work on the aarch64-gnu port, aka GNU/Hurd on 64-bit ARM.
>
> 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
On Wed, Jan 3, 2024 at 9:15 AM Sergey Bugaev wrote:
>
> Hello!
>
> This is my work on the aarch64-gnu port, aka GNU/Hurd on 64-bit ARM.
>
> 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
On Wed, Jan 3, 2024 at 8:30 PM Joseph Myers wrote:
> 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
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.
> The
