Hello,
Answering on just a couple of things for now, while I have the
information at hand.
Mike Kelly, le sam. 21 févr. 2026 09:23:12 +0000, a ecrit:
> 1) Certain compilations refer to the contents of a header file that when
> parsed
> find corrupt contents. This presents as compilation failure with error reports
> like:
>
> /usr/include/i386-gnu/bits/types/clock_t.h:1:3: error: stray ‘\2’ in program
>
> This has previously been seen in qtcreator, sysprof and others. I found some
> errors like this from build logs as far back as 2024 so it's not a recent
> development. I've witnessed this on 1 occasion on my personal machine whilst
> compiling gnumach.
It's not only headers, I also notice it on perl files:
assimp_6.0.4+ds-1+b1_hurd-i386-2026-02-09T20:30:53Z
assimp_6.0.4+ds-1+b1_hurd-i386-2026-02-10T14:34:22Z
binutils-embedded_28_hurd-i386-2026-02-12T02:28:03Z
gcc-riscv64-unknown-elf_23_hurd-i386-2026-02-12T03:02:37Z
ginac_1.8.10-1_hurd-i386-2026-02-12T01:24:18Z
octave-tablicious_0.4.5-3_hurd-i386-2026-02-12T02:37:40Z
haskell-http-semantics_0.3.0-1_hurd-amd64-2026-02-11T07:25:00Z
haskell-lambdahack_0.11.0.1-2+b1_hurd-amd64-2026-02-21T22:21:03Z
ismrmrd_1.15.0-1_hurd-amd64-2026-02-21T23:06:18Z
mothur_1.48.5-2_hurd-amd64-2026-02-11T06:22:31Z
ruby-sqlite3_2.9.0-1_hurd-amd64-2026-02-11T07:35:16Z
rust-glib_0.21.5-2_hurd-amd64-2026-02-11T07:31:12Z
> The double signal fix is included in libc0.3 (2.42-12). That helped the main
> haskell compiler (ghc) package build but hasn't helped with issue 2. Does
> issue
> 1 also still occur in builds made with the latest glibc?
I haven't seen any issue in headers since then, but I have seen issues
on perl files.
Note that I have only seen issue 2 on amd64.
> The problems are seen on the buildd machines more frequently than on mine.
> This
> might be down to relatively poor performance of my machine or some subtle
> difference in the machine or software configuration.
The boralus buildd for instance is hosted by an Intel(R) Xeon(R) CPU D-1521 @
2.40GHz
That could be the qemu configuration, here it is:
/usr/bin/qemu-system-x86_64 -machine
pc-q35-7.2,usb=off,mem-merge=off,memory-backend=pc.ram,acpi=on -accel kvm -cpu
qemu64,x2apic=on,hypervisor=on,lahf-lm=on,svm=off -m size=3145728k -overcommit
mem-lock=on -smp 1,sockets=1,cores=1,threads=1 -no-user-config -nodefaults -rtc
base=utc -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -device
{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}
-device
{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}
-device
{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}
-device
{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}
-device
{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}
-device
{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}
-device
{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}
-device
{"driver":"pcie-root-port","port":23,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x2.0x7"}
-device
{"driver":"pcie-root-port","port":24,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x3"}
-device
{"driver":"pcie-root-port","port":25,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x3.0x1"}
-device
{"driver":"pcie-root-port","port":26,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x3.0x2"}
-device
{"driver":"pcie-root-port","port":27,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x3.0x3"}
-device
{"driver":"pcie-root-port","port":28,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x3.0x4"}
-device
{"driver":"pcie-root-port","port":29,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x3.0x5"}
-device {"driver":"qemu-xhci","id":"usb","bus":"pci.2","addr":"0x0"} -device
{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.3","addr":"0x0"}
-blockdev
{"driver":"file","filename":"/home/kvm/boralus/hd0.img","node-name":"libvirt-1-storage","read-only":false,"cache":{"direct":false,"no-flush":false}}
-device
{"driver":"ide-hd","bus":"ide.0","drive":"libvirt-1-storage","id":"sata0-0-0","bootindex":1,"write-cache":"on"}
-netdev {"type":"tap","fd":"37","id":"hostnet0"} -device
{"driver":"pcnet","netdev":"hostnet0","id":"net0","mac":"02:00:00:83:05:37","bus":"pci.1","addr":"0x0"}
-chardev pty,id=charserial0 -device
{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}
-audiodev {"id":"audio1","driver":"none"} -vnc
vnc=unix:/home/kvm/boralus/vnc_socket,audiodev=audio1 -k fr -device
{"driver":"cirrus-vga","id":"video0","bus":"pcie.0","addr":"0x1"} -global
ICH9-LPC.noreboot=off -watchdog-action reset -incoming defer -device
{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.4","addr":"0x0"}
-sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg
timestamp=on
> It would make solving these problems simpler with a regularly failing test
> case. I wonder if there's anything that might be gained by trying to setup a
> test buildd machine even though it seems unlikely that would do much
> differently than just using sbuild or pbuilder directly?
A buildd machine is nothing really different from a machine that just
runs sbuild :)
We use type=plain schroot chroots, with eatmydata.
Samuel
