On Thu, Nov 19, 2026 at 5:11 PM Diego Nieto Cid <[email protected]> wrote: > It seems to me that install-data from gnumach does not > install the link from mach/machine to mach/i386. Because > after creating it manually, the build succeeds. > > So, should gnumach be taught to install the link? > I can have a look, but it must wait for later.
A quick grep finds install-data-hook in gnumach:Makefrag.am, so this is already supposed to be happening, and probably was working for me when I posted this. Two other adjustments since you're looking into this: 1. if you pass --prefix=$PREFIX to glibc, hurd etc like I suggested, files gets installed into the expected places, and this works as a cross-build environment to then build other software in. However if you're planning to directly use the built glibc etc, at runtime they would also expect to find things in $PREFIX which is of course the wrong place. So you likely want something like --prefix= (empty line), then DESTDIR=$PREFIX when installing instead. There were some issues related to that as well, I think you had to go and manually fix up libc.so (the textual link script) after this. 2. Mixing "build" (e.g. x86_64-linux-gnu) and "host" (e.g. aarch64-gnu) binaries in the same $PREFIX/bin directory is not great. Examples of the former are the executables of the cross-toolchain, examples of the latter are glibc and Hurd binaries that we install. So ideally we'd create a separate bin dir for the former ones, e.g. $PREFIX/host-bin (where host means "build") and pass that as --bindir (or whatever was the appropriate knob in autoconf), and that would be what you'd be adding to PATH, not $PREFIX/bin. Sergey
