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.08::gentoo failed (configure phase): * (no error message) * * Call stack: * ebuild.sh, line 127: Called src_configure ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma_systemd-j4-20210826-120009 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * clang version 12.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.1 Python 3.9.6 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.54.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit 92082531343adedd2c80f9b6879a6f99c1688325 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sun Aug 29 17:06:55 2021 +0000 2021-08-29 17:06:51 UTC emerge -qpvO dev-lang/moarvm [ebuild N ] dev-lang/moarvm-2021.08 USE="clang jit ubsan (-asan) -debug -doc -optimize -static-libs"
Created attachment 736681 [details] emerge-info.txt
Created attachment 736684 [details] dev-lang:moarvm-2021.08:20210829-175714.log
Created attachment 736687 [details] emerge-history.txt
Created attachment 736690 [details] environment
Created attachment 736693 [details] etc.portage.tar.bz2
Created attachment 736696 [details] logs.tar.bz2
Created attachment 736699 [details] temp.tar.bz2
The code around this check has this: if (!$can_compile || !$can_link) { die "ERROR\n\n" . " Can't " . ($can_compile ? 'link' : 'compile') . " simple C program.\n" . " Failing command: $command_errored\n" . " Error: $error_message\n\n" . "Cannot continue after this error.\n" . "On linux, maybe you need something like 'sudo apt-get install build-essential'.\n" . "On macOS, maybe you need to install XCode and accept the XCode EULA.\n"; } So it should show you what failed - worst case you can just try running build/probe.pm by hand. Works for me, no idea how to reproduce, no idea why it wants to fail for you.
