checking for alloca... no checking stack direction for C alloca... -1 checking whether the preprocessor supports include_next... yes checking whether source code line length is unlimited... yes checking for C/C++ restrict keyword... __restrict__ checking whether <wchar.h> uses 'inline' correctly... no configure: error: <wchar.h> cannot be used with this compiler (clang -O3 -pipe -march=native -fno-diagnostics-color -Werror=implicit-function-declaration -Werror=implicit-int -fno-strict-aliasing ). This is a known interoperability problem of glibc <= 2.5 with gcc >= 4.3 in C99 mode. You have four options: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_llvm-20240411-061503 ------------------------------------------------------------------- CC=clang CXX=clang++ gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 18.1.3+libcxx Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/18/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/18 18.1.3+libcxx Python 3.11.9 Available Ruby profiles: [1] ruby31 (with Rubygems) [2] ruby33 (with Rubygems) * Available Rust versions: [1] rust-bin-1.77.1 * The following VMs are available for generation-2: The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): go version go1.22.2 linux/amd64 HEAD of ::gentoo commit 8bd92422bc397f667079d904b343696a541e0d24 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Apr 13 16:19:09 2024 +0000 2024-04-13 16:19:08 UTC emerge -qpvO net-analyzer/monitoring-plugins [ebuild N ] net-analyzer/monitoring-plugins-2.3.5 USE="ipv6 postgres ssl -curl -dns -fping -game -gnutls -ldap -mysql -radius -samba -snmp -ssh"
Created attachment 890732 [details] emerge-info.txt
Created attachment 890733 [details] emerge-history.txt
Created attachment 890734 [details] environment
Created attachment 890735 [details] etc.clang.tar.xz
Created attachment 890736 [details] etc.portage.tar.xz
Created attachment 890737 [details] logs.tar.xz
Created attachment 890738 [details] net-analyzer:monitoring-plugins-2.3.5:20240413-171541.log
Created attachment 890739 [details] qlist-info.txt.xz
Created attachment 890740 [details] temp.tar.xz
The real errors here are e.g. ld.lld: error: /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../lib64/Scrt1.o is incompatible with elf32-i386 ld.lld: error: /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../lib64/crti.o is incompatible with elf32-i386 ld.lld: error: /usr/lib/llvm/18/bin/../../../../lib/clang/18/lib/linux/clang_rt.crtbegin-x86_64.o is incompatible with elf32-i386 ld.lld: error: conftest1.o is incompatible with elf32-i386 ld.lld: error: conftest2.o is incompatible with elf32-i386 There were many similar reports filed around this time for other packages -- something was messed up on the tinderbox.
As with nagios-plugins, this turned out to be a real problem with USE=postgres on multilib systems using lld. Fortunately the fix for nagios-plugins applied cleanly to monitoring-plugins.
