Adding extra include for libffi: -I/usr/lib64/libffi/include OK probing whether your compiler thinks that it is gcc Can't compile simple gcc probe, so something is badly wrong at build/probe.pm line 206. * ERROR: dev-lang/moarvm-2021.10::gentoo failed (configure phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-j4-20220106-060005 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang version 13.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.9 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.57.0 * The following VMs are available for generation-2: *) AdoptOpenJDK JRE 11.0.13_p8 [openjdk-jre-bin-11] Available Java Virtual Machines: [1] openjdk-jre-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: HEAD of ::gentoo commit 1537083cb3e3e4e0c9c5c674584d0b62d2293bba Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Jan 10 04:36:53 2022 +0000 2022-01-10 04:36:51 UTC emerge -qpvO dev-lang/moarvm [ebuild N ] dev-lang/moarvm-2021.10 USE="clang optimize ubsan (-asan) -debug -doc -jit -static-libs"
Created attachment 761759 [details] emerge-info.txt
Created attachment 761760 [details] dev-lang:moarvm-2021.10:20220110-053636.log
Created attachment 761761 [details] emerge-history.txt
Created attachment 761762 [details] environment
Created attachment 761763 [details] etc.portage.tar.bz2
Created attachment 761764 [details] logs.tar.bz2
Created attachment 761765 [details] temp.tar.bz2
> Can't compile simple gcc probe, so something is badly wrong at build/probe.pm line 206. That looks like a pretty broken toolchain configuration to me
appeared recently at the tinderbox image 17.1_desktop_plasma_systemd-j4-20220112-090006
Created attachment 762285 [details] emerge-info.txt
Created attachment 762286 [details] dev-lang:moarvm-2021.10:20220115-225535.log
Created attachment 762288 [details] emerge-history.txt
Created attachment 762289 [details] environment
Created attachment 762290 [details] etc.portage.tar.bz2
Created attachment 762291 [details] logs.tar.bz2
Created attachment 762292 [details] temp.tar.bz2
tinderbox_musl has reproduced this issue with version 2023.12 - Updating summary.
On my system this appears to be an issue with dev-libs/mimalloc. manually running this config step gave me: /usr/bin/x86_64-pc-linux-gnu-ld.bfd: cannot find -lmimalloc: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) my copy has installed mimalloc-valgrind.so but not mimalloc.so. The only way I can get this to have mimalloc.so is to not use the valgrind flag on dev-libs/mimalloc. This seems to be some conflict between moarvm and the valgrind USE flag, or possibly with dev-libs/mimalloc itself. Once I have merged dev-libs/mimalloc without USE="valgrind" then dev-lang/moarvm merges successfully.
