checking for Build JDK... yes, will use output dir configure: Using default toolchain gcc (GNU Compiler Collection) configure: error: in `/var/tmp/portage/dev-java/openjdk-11.0.9_p11/work/jdk11u-jdk-11.0.9-ga': configure: error: no acceptable C compiler found in $PATH See `config.log' for more details configure exiting with result code 1 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-libressl-20201012-031827 ------------------------------------------------------------------- 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) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.47.0 [2] rust-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 Fri Oct 23 06:05:29 AM UTC 2020 /var/db/repos/libressl Sun Oct 18 04:35:14 PM UTC 2020 emerge -qpvO dev-java/openjdk [ebuild N ] dev-java/openjdk-11.0.9_p11 USE="alsa cups jbootstrap pch -debug -doc -examples (-gentoo-vm) -headless-awt -javafx (-selinux) -source -systemtap"
Created attachment 668069 [details] emerge-info.txt
Created attachment 668072 [details] dev-java:openjdk-11.0.9_p11:20201023-075022.log
Created attachment 668075 [details] emerge-history.txt
Created attachment 668078 [details] environment
Created attachment 668081 [details] etc.portage.tbz2
Created attachment 668084 [details] logs.tbz2
Created attachment 668087 [details] temp.tbz2
This has most likely been fixed by some changes in the final autoconf-2.70 release.