On 2026-01-27, Erwan RIGOLLOT wrote: > Hello Everybody > > I make a lot of updates of my system with emerge @world. > > emerge zig failed with: > build_runner.zig file_hash Unexpected > > So I emerge zib-bin > > Now lattest packages failed : >>>> Emerging (1 of 1) sys-fs/ncdu-2.9.1::gentoo > * ncdu-2.9.1.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] > * Searching Zig 0.14... > * ERROR: sys-fs/ncdu-2.9.1::gentoo failed (setup phase): > * Could not find (suitable) Zig at "/usr/bin"
Coffee hasn't fully kicked in, so I may be misreading this. At this point, it looks to me the only way for this to fail if you do have an executable /usr/bin/zig-bin-0.14.1 is if the command that checks for LLVM support fails. (I don't know Zig, so I have no idea what the LLVM part needs besides having it installed. There doesn't seem to be a USE flag in zig-bin for that.) https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/zig-utils.eclass#n518 (And more specifically lines 522-523 on the file above, as required below:) https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-fs/ncdu/ncdu-2.9.1.ebuild#n9 > * > * Call stack: > * ebuild.sh, line 143: Called pkg_setup > * ebuild.sh, line 379: Called zig_pkg_setup > * zig.eclass, line 330: Called zig-utils_setup > * zig-utils.eclass, line 557: Called zig-utils_find_installation > * zig-utils.eclass, line 532: Called die > * The specific snippet of code: > * die "Could not find (suitable) Zig at \"${base_path}\"" > * > * If you need support, post the output of `emerge --info > '=sys-fs/ncdu-2.9.1::g entoo'`, > * the complete build log and the output of `emerge -pqv > '=sys-fs/ncdu-2.9.1::ge ntoo'`. > * The complete build log is located at > '/var/tmp/portage/sys-fs/ncdu-2.9.1/temp /build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/sys-fs/ncdu-2.9.1 /temp/die.env'. > * Working directory: '/var/tmp/portage/sys-fs/ncdu-2.9.1/empty' > * S: '/var/tmp/portage/sys-fs/ncdu-2.9.1/work/ncdu-2.9.1' -- Nuno Silva
