Hello Nik, Thank you for getting back to me.
On Mon, Aug 31, 2026 at 09:18:06AM -0400, Nikolas Nyby wrote: > Thanks for looking into this. It looks like this was addressed upstream > here by the Dillo maintainer: > > https://git.dillo-browser.org/dillo/commit/?id=b43ab26e81a1e399e3cb148b972a284518aa4d39 > > If this simpler upstream patch doesn't fully resolve the Hurd build > failure we can certainly resolve that in a custom debian patch as well. > Even then, these patches could be forwarded upstream. That commit will make the code build on the hurd, but it is not the preferred way to handle this type of issues, and dynamic allocation is preferred https://www.gnu.org/software/hurd/faq/foo_max Would upstream consider a different approach? Best regards, João
