Summary: | dev-lang/zig-0.11.0 - Failed to run command: ./stage3/bin/zig build std-docs --prefix /var/tmp/portage/dev-lang/zig-0.11.0/work/zi | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Eric Joldasov <bratishkaerik> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/33272 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
dev-lang:zig-0.11.0:20230913-061551.log emerge-history.txt environment etc.clang.tar.xz etc.portage.tar.xz |
Description
Toralf Förster
2023-09-13 08:14:19 UTC
Created attachment 870467 [details]
emerge-info.txt
Created attachment 870468 [details]
dev-lang:zig-0.11.0:20230913-061551.log
Created attachment 870469 [details]
emerge-history.txt
Created attachment 870470 [details]
environment
Created attachment 870471 [details]
etc.clang.tar.xz
Created attachment 870472 [details]
etc.portage.tar.xz
Weird, I didn't get email about this bug! Sorry for that. I cannot reproduce it, but looks like "./stage3/bin/zig" binary has broken dynamic linking (most propably libc, typical warnings are also here)? If that's the case, then this will be fixed by fixing libc detection. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2b7185f8742031e9a7acfa5d5e837fc48daaeccd commit 2b7185f8742031e9a7acfa5d5e837fc48daaeccd Author: Eric Joldasov <bratishkaerik@getgoogleoff.me> AuthorDate: 2023-10-20 17:06:17 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-10-27 02:53:04 +0000 dev-lang/zig: add simple `zig env` invocation to check if compiler built itself properly Will make bugs similar to following easier to spot in future because they will fall earlier and with better error message [than "`zig build std-docs` not found"]. In case "doc" USE-flag and tests are disabled, miscompilation could have been unnoticed by user at all until Zig usage, since the only calls to Zig binary in ebuild would have been skipped. Now, it will always check during "src_compile" phase and can reveal potentially hidden bug. Bug: https://bugs.gentoo.org/914101 Signed-off-by: Eric Joldasov <bratishkaerik@getgoogleoff.me> Signed-off-by: Sam James <sam@gentoo.org> dev-lang/zig/zig-0.11.0-r1.ebuild | 2 ++ dev-lang/zig/zig-9999.ebuild | 2 ++ 2 files changed, 4 insertions(+) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=42ac667416fe133255c3baca620e9af61315cb3b commit 42ac667416fe133255c3baca620e9af61315cb3b Author: Eric Joldasov <bratishkaerik@getgoogleoff.me> AuthorDate: 2023-10-10 03:12:16 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-10-27 02:53:03 +0000 dev-lang/zig: patch 0.11.0 to use getconf when detecting glibc version Bug: https://bugs.gentoo.org/914731 Bug: https://bugs.gentoo.org/914101 Signed-off-by: Eric Joldasov <bratishkaerik@getgoogleoff.me> Signed-off-by: Sam James <sam@gentoo.org> .../zig/files/zig-0.11.0-first-try-getconf.patch | 109 +++++++++++++++++++++ .../{zig-0.11.0.ebuild => zig-0.11.0-r1.ebuild} | 4 + 2 files changed, 113 insertions(+) |