checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu configure: error: in `/var/tmp/portage/net-misc/ntp-4.2.8_p15/work/ntp-4.2.8p15': configure: error: no acceptable C compiler found in $PATH See `config.log' for more details ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-libressl_abi32+64-20201012-091521 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) [5] pypy3 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.47.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.265_p01 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed Oct 21 11:05:29 PM UTC 2020 /var/db/repos/libressl Sun Oct 18 04:35:14 PM UTC 2020 emerge -qpvO net-misc/ntp [ebuild N ] net-misc/ntp-4.2.8_p15 USE="ipv6 libressl readline ssl threads -caps -debug -openntpd -parse-clocks -samba (-selinux) -snmp -vim-syntax -zeroconf"
Created attachment 667865 [details] emerge-info.txt
Created attachment 667868 [details] emerge-history.txt
Created attachment 667871 [details] environment
Created attachment 667874 [details] etc.portage.tbz2
Created attachment 667877 [details] logs.tbz2
Created attachment 667880 [details] net-misc:ntp-4.2.8_p15:20201022-001340.log
Created attachment 667883 [details] temp.tbz2
Alright final autoconf-2.70 release seems to no longer causing configure script to fail. BUT it seems like it is triggering maintainer-mode unconditionally...
Nevermind, I was wrong with maintainer-mode. It just got "magically" fixed by using autoconf-2.70 final release.