Build type: native build Project name: serd Project version: 0.30.14 ../serd-0.30.14/meson.build:4:0: ERROR: Unknown compiler(s): [['clang']] A full log can be found at /var/tmp/portage/dev-libs/serd-0.30.14-r1/work/serd-0.30.14-abi_x86_64.amd64/meson-logs/meson-log.txt ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-j4-20220916-040004 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12.2.0 * clang/llvm (if any): clang version 15.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/15/bin /usr/lib/llvm/15 15.0.0 Python 3.10.7 Available Ruby profiles: [1] ruby27 (with Rubygems) [2] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.63.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.4.1_p1 [openjdk-bin-17] Available Java Virtual Machines: [1] openjdk-bin-17 system-vm The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): GNU Make 4.3.90 HEAD of ::gentoo commit cf2b335b975c83d55eec561b3f6e6014621cc9ec Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Fri Sep 16 17:02:01 2022 +0000 2022-09-16 17:02:01 UTC emerge -qpvO dev-libs/serd [ebuild N ] dev-libs/serd-0.30.14-r1 USE="tools -doc -static-libs -test" ABI_X86="(64) -32 (-x32)"
Created attachment 805972 [details] emerge-info.txt
Created attachment 805975 [details] dev-libs:serd-0.30.14-r1:20220916-180929.log
Created attachment 805978 [details] emerge-history.txt
Created attachment 805981 [details] environment
Created attachment 805984 [details] etc.portage.tar.bz2
Created attachment 805987 [details] logs.tar.bz2
Created attachment 805990 [details] temp.tar.bz2
in logs.tar.bz2 -> meson-logs/meson-log.txt ``` Detecting compiler via: clang --version compiler returned <Popen: returncode: 0 args: ['clang', '--version']> compiler stdout: compiler stderr: ../serd-0.30.14/meson.build:4:0: ERROR: Unknown compiler(s): [['clang']] ``` This clang command is successfully exiting, without emitting any content on stdout/stderr, even when asked to do so. From temp.tar.bz2, it seems clang is a wrapper script that redirects all output to a log file clang14.log / clang15.log, and then to /dev/null; these two log files are also in that tarball, and contain the output that Meson expected to see for the --version information. The wrapper script is really weird: ``` # Non-Autoconf configure scripts might try to parse stderr/stdout, so just run # it again... if [[ -f configure ]] && ! grep -q "#.*Generated by Autoconf" configure ; then clang-15 $@ else exit ${x[0]} fi ``` Only configure scripts? And what do those do -- just run every compilation twice?, so packages build half as fast? :o Anyway, Meson does assuredly parse stdout/stderr, so at least check for that too.
yes, see the tracker bug for details and motivation, obviously this isn't a meson issue and it's the wrapper being too cheesy. I'll have a play in a bit (probably have one of them emit output and not the other). The duplicates are fine, I'll just en-masse mark them as such later.
(Thinking about it, I'm not sure why i didn't end up just always execing again!)
Ah, I see, even the wrapper itself is just a temporary thing. Didn't realize that.
*** Bug 870532 has been marked as a duplicate of this bug. ***
*** Bug 870511 has been marked as a duplicate of this bug. ***
*** Bug 870508 has been marked as a duplicate of this bug. ***
*** Bug 870496 has been marked as a duplicate of this bug. ***
*** Bug 870505 has been marked as a duplicate of this bug. ***
*** Bug 870469 has been marked as a duplicate of this bug. ***
(In reply to Eli Schwartz from comment #11) > Ah, I see, even the wrapper itself is just a temporary thing. Didn't realize > that. no problem & sorry for the noise! Latest version of wrapper should be OK, just need toralf to pull it down.
Fixed.
*** Bug 870562 has been marked as a duplicate of this bug. ***
Not related to C99
