IRC channel logs

2026-01-30.log

back to list of logs

<gnu_srs1>youpi: Something might be wrong with mahler. All packages building fails.
<youpi>gnu_srs1: that happens sometimes when the chroot gets corrupted
<youpi>I'll recreate it
<youpi>damo22: thinking about it: it would be useful to CI-test the build with --enable-platform=xen
<damo22>ah yes
<damo22>that does not have apic right?
<youpi>nope
<youpi>I don't remember who asked about qemu-on-hurd:
<youpi> https://lists.gnu.org/archive/html/bug-hurd/2024-01/msg00153.html
<bjorkintosh>ON?
<bjorkintosh>in. for me.
<bjorkintosh>I'm running hurd in qemu (via proxmox)
<nexussfan>qemu in hurd should always work
<nexussfan>*hurd in qemu
<youpi>qemu-running-in-hurd, not the converse
<nexussfan>qemu running INSIDE hurd would be nice
<nexussfan>But we already have childhurds
<bjorkintosh>oh? how do those work, nexussfan?
<youpi>that's not enough to run the gnumach check suite
<nexussfan>true
<bjorkintosh>by design?
<nexussfan>bjorkintosh: Hurd inside hurd
<bjorkintosh>or by lack of features?
<nexussfan>the gnumach tests require running it's own gnumach
<nexussfan>afaik
<youpi>yes, that's the point: testing the kernel, so it needs virtual hardware for that
<damo22>ok it seems those patches never got picked up and made into v3
<damo22>i could collate them and address the comments and then submit v3?
<youpi>that'd be useful
<damo22>cool, one of the patches is already upstreamed, but independently
<damo22>the syscall fix is already done
<damo22>compiling...
<damo22>hmm but there is a slight difference upstream that broke it stil
<damo22>ok fixed
<damo22>i have working qemu
<damo22>mailed in working qemu
<damo22>the patches made it to their list https://lore.kernel.org/qemu-devel/20260130031954.1661880-1-damien@zamaudio.com/T/
<nexussfan>`#define PATH_MAX 1024`
<nexussfan>Surely this is not a good idea
<damo22>no, i dont have time to write code that removes it
<nexussfan>Isn't there a path_max alternative for hurd? Let me check glibc
<damo22>you have to malloc space for the path and fix it everywhere
<damo22>hence the commit msg
<nexussfan>What about FILENAME_MAX?
<nexussfan>> Unlike PATH_MAX, this macro is defined even if there is no actual limit imposed. In such a case, its value is typically a very large number. This is always the case on GNU/Hurd systems.
<damo22>i dont know what the deal is with that parameter but getting a basic qemu is more important than fixing path lengths
<nexussfan>True
<damo22>if you want to remove the restriction, patch welcome
<yelninei>Hi, has anyone tried dlang on hurd? gdc 11 seems to build but phobos seems unsupported