Diego Nieto Cid, le mer. 21 mai 2025 23:57:26 +0100, a ecrit: > Now I have a few issues building GLIBC. > > 1. I added the following checks to sysdeps/mach/configure.ac > > mach_RPC_CHECK(gnumach.defs, vm_set_size_limit, > HAVE_MACH_VM_SET_SIZE_LIMIT) > mach_RPC_CHECK(gnumach.defs, vm_get_size_limit, > HAVE_MACH_VM_GET_SIZE_LIMIT) > > However, I don't know how to generate the corresponding configure file.
It's the autoreconf command. > 2. After make install the system was broken, Oops, running make install from a glibc build will indeed usually break the system, yes, since upstream's files layout most often do not match your distribution's files layout. > make[3]: Leaving directory '/home/demo/dev/hurd/upstream/glibc/elf' > /usr/bin/install -c > /home/demo/dev/hurd/upstream/glibc-build/elf/ld.so /lib/ld-x86-64.so.1.new > mv -f /lib/ld-x86-64.so.1.new /lib/ld-x86-64.so.1 > .././scripts/mkinstalldirs /usr/lib/audit > make[2]: *** [Makefile:264: /usr/lib/audit/sotruss-lib.so] Killed > make[2]: Leaving directory '/home/demo/dev/hurd/upstream/glibc/elf' > make[1]: *** [Makefile:484: elf/subdir_install] Error 2 > make[1]: Leaving directory '/home/demo/dev/hurd/upstream/glibc' > make: *** [Makefile:36: install] Error 2 > demo@debian:~/dev/hurd/upstream/glibc-build$ ls > Killed > > Do I need to apply some patch/es to the sourceware repository for Hurd? It's much more involved than that, probably some configure flags etc. But you do not need to install it though: you can use the testrun.sh script generated by make check, to run programs with your newly-built libc. If all this is not already documented on the hurd wiki in some glibc page, it'll probably be useful to add it. Samuel
