>>> Compiling source in /var/tmp/portage/sys-fs/ncdu-2.3/work/ncdu-2.3 ... make -j5 /usr/bin/zig-0.11.0 build -Doptimize=ReleaseFast make: /usr/bin/zig-0.11.0: No such file or directory make: *** [Makefile:20: release] Error 127 * ERROR: sys-fs/ncdu-2.3::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=sys-fs/ncdu-2.3::gentoo'`, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_systemd-20230821-235016 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 16.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/16 16.0.6 Python 3.11.5 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.71.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.19_p7 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.7_p7 [openjdk-bin-17] *) Eclipse Temurin JDK 8.372_p07 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm [2] openjdk-bin-11 [3] openjdk-bin-17 php cli (if any): go version go1.21.0 linux/amd64 HEAD of ::gentoo commit a90cb47817fbf72acfba3624227da9c09a24e642 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Fri Aug 25 05:16:34 2023 +0000 2023-08-25 05:16:33 UTC emerge -qpvO sys-fs/ncdu [ebuild N ] sys-fs/ncdu-2.3 USE="-verify-sig"
Created attachment 868696 [details] emerge-info.txt
Created attachment 868697 [details] emerge-history.txt
Created attachment 868698 [details] environment
Created attachment 868699 [details] etc.clang.tar.xz
Created attachment 868700 [details] etc.portage.tar.xz
Created attachment 868701 [details] sys-fs:ncdu-2.3:20230825-060022.log
Created attachment 868702 [details] temp.tar.xz
Hello, could you please re-test this again with latest dev-lang/zig-0.11.0 ebuild? I suspect `No such file or directory` refers to Zig executable's invalid ELF interpreter path. Thanks in advance.
(In reply to Eric Joldasov from comment #8) > Hello, could you please re-test this again with latest dev-lang/zig-0.11.0 > ebuild? I suspect `No such file or directory` refers to Zig executable's > invalid ELF interpreter path. Thanks in advance. I'm not able to reproduce this issue anymore so I will go ahead and close the bug. Thanks!
