* USE: abi_x86_64 amd64 crossdev-mingw d3d11 d3d9 dxgi elibc_glibc kernel_linux userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * With USE=crossdev-mingw, it is necessary to setup the mingw toolchain. * For instructions, please see: https://wiki.gentoo.org/wiki/Mingw * ERROR: app-emulation/dxvk-1.10.1::gentoo failed (pretend phase): * USE=crossdev-mingw is set but x86_64-w64-mingw32-g++ was not found * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib_hardened-j4-20220518-230015 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-10.3.1 [3] x86_64-pc-linux-gnu-12.1.1 * clang/llvm (if any): clang version 14.0.3 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.3 Python 3.9.13 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.60.0 [2] rust-1.60.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.15_p10 [openjdk-bin-11] *) Eclipse Temurin JDK 17.0.3_p7 [openjdk-bin-17] 3) Eclipse Temurin JDK 8.332_p09 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: HEAD of ::gentoo commit b919e03dc4931a29bc0a5b1dfe87120522104276 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon May 23 12:33:02 2022 +0000 2022-05-23 12:33:01 UTC emerge -qpvO app-emulation/dxvk [ebuild N ] app-emulation/dxvk-1.10.1 USE="crossdev-mingw d3d9 d3d11 dxgi -d3d10 -debug"
Created attachment 780389 [details] emerge-info.txt
Created attachment 780392 [details] app-emulation:dxvk-1.10.1:20220523-132547.log
Created attachment 780395 [details] die.env
Created attachment 780398 [details] emerge-history.txt.bz2
Created attachment 780401 [details] etc.portage.tar.bz2
Created attachment 780404 [details] logs.tar.bz2
I guess this is an expected behavior