Andreas Enge <andr...@enge.fr> writes:
> Just a one-package-failure-report: zig fails on core-updates, and I do not
> see why from the error message. If someone who knows the package could have
> a look, that would be great.
No solution, but maybe some pointers:
It seems like the installed `zig` binary segfaults.
This is the build failure message:
--8<---------------cut here---------------start------------->8---
starting phase `check'
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program:
"/gnu/store/8pd12pn8n3ganc3y4776m44gjrfdvlvd-zig-0.10.1/bin/zig" arguments:
("build" "test" "-Dskip-stage1" "-Dskip-stage2-tests" "-Dskip-non-native")
exit-status: #f term-signal: 11 stop-signal: #f>
phase `check' failed after 0.0 seconds
command "/gnu/store/8pd12pn8n3ganc3y4776m44gjrfdvlvd-zig-0.10.1/bin/zig"
"build" "test" "-Dskip-stage1" "-Dskip-stage2-tests" "-Dskip-non-native" failed
with signal 11
--8<---------------cut here---------------end--------------->8---
When invoking the installed binary directly:
--8<---------------cut here---------------start------------->8---
$ /gnu/store/8pd12pn8n3ganc3y4776m44gjrfdvlvd-zig-0.10.1/bin/zig
Segmentation fault
--8<---------------cut here---------------end--------------->8---
I'm afraid, I don't know anything about debugging segfaults.
A hunch: This might have something to do with Zig not properly
supporting glibc 2.35: https://github.com/ziglang/zig/issues/12808
-pukkamustard
