Hello again, libdrm still FTBFS on GNU/Hurd, now ate 2.4.108-1. Attached are two updated patches, hurd-port.diff and path_max.diff.
libdrm-2.4.108-1 (and 2.4.104-1) has been built and tested fine on GNU/Linux and GNU/Hurd. On Linux the patches have also been tested with valgrind using the package drm-info, depending on libdrm2. With the previous patch for path_max the bug reported in #975658 has been verified with the program drm_info. The patches are now valgrind-clean: valgrind drm_info ... ==8475== HEAP SUMMARY: ==8475== in use at exit: 0 bytes in 0 blocks ==8475== total heap usage: 1,891 allocs, 1,891 frees, 277,802 bytes allocated ==8475== ==8475== All heap blocks were freed -- no leaks are possible ==8475== ==8475== For lists of detected and suppressed errors, rerun with: -s ==8475== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) (Compiling xf86drm.c still causes a lot of warnings, but these are already present in the upstream code.) Thanks!