fatal: not a git repository (or any parent up to mount point /var/tmp) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). -- Found PkgConfig: /usr/bin/x86_64-gentoo-linux-musl-pkg-config (found version "1.8.0") -- Detected distribution: gentoo:"2.8" CMake Error at CMakeLists.txt:162 (find_library): Could not find LIBC using the following names: libc.so.6 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-j4-20220701-080004 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-12.1.1 * clang/llvm (if any): /usr/lib/llvm/14 14.0.6 Python 3.9.13 Available Ruby profiles: [1] ruby27 (with Rubygems) [2] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.62.0 [2] rust-1.62.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.3_p7 [openjdk-bin-17] Available Java Virtual Machines: [1] openjdk-bin-17 system-vm php cli: [1] php7.4 * [2] php8.0 [3] php8.1 HEAD of ::gentoo commit 63ecaeace856800df101bb70dd1e64d0cb002b3b Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jul 2 11:31:29 2022 +0000 2022-07-02 11:31:29 UTC emerge -qpvO dev-libs/roct-thunk-interface [ebuild N ] dev-libs/roct-thunk-interface-5.0.2
Created attachment 789578 [details] emerge-info.txt
Created attachment 789581 [details] CMakeOutput.log
Created attachment 789584 [details] dev-libs:roct-thunk-interface-5.0.2:20220702-123837.log
Created attachment 789587 [details] emerge-history.txt
Created attachment 789590 [details] environment
Created attachment 789593 [details] etc.portage.tar.bz2
Created attachment 789596 [details] logs.tar.bz2
Created attachment 789599 [details] temp.tar.bz2
tinderbox_musl has reproduced this issue with version 5.3.3 - Updating summary.
What's the difference between this bug and https://bugs.gentoo.org/show_bug.cgi?id=865799 ? Both seem to refer to the same error.
*** This bug has been marked as a duplicate of bug 865799 ***