checking for working fork... yes checking for working vfork... (cached) yes configure: error: cannot run /bin/sh ./config.sub !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-process/tiptop-2.3.1/work/tiptop-2.3.1/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20201019-041507 ------------------------------------------------------------------- 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: (none found) 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 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Fri Oct 23 01:07:12 PM UTC 2020 emerge -qpvO sys-process/tiptop [ebuild N ] sys-process/tiptop-2.3.1
Created attachment 668177 [details] emerge-info.txt
Created attachment 668180 [details] emerge-history.txt
Created attachment 668183 [details] environment
Created attachment 668186 [details] etc.portage.tbz2
Created attachment 668189 [details] logs.tbz2
Created attachment 668192 [details] sys-process:tiptop-2.3.1:20201023-165100.log
Created attachment 668195 [details] temp.tbz2
This has most likely been fixed by some changes in the final autoconf-2.70 release.