checking for working fork... yes checking for working vfork... (cached) yes configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.." !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-db/redis-6.0.6/work/redis-6.0.6/config.log ------------------------------------------------------------------- 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-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) 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 Sun Oct 18 04:05:22 PM UTC 2020 /var/db/repos/libressl Fri Oct 9 07:35:07 PM UTC 2020 emerge -qpvO dev-db/redis [ebuild N ] dev-db/redis-6.0.6 USE="jemalloc -luajit -tcmalloc -test"
Created attachment 666590 [details] emerge-info.txt
Created attachment 666593 [details] dev-db:redis-6.0.6:20201018-170444.log
Created attachment 666596 [details] emerge-history.txt
Created attachment 666599 [details] environment
Created attachment 666602 [details] etc.portage.tbz2
Created attachment 666605 [details] logs.tbz2
Created attachment 666608 [details] temp.tbz2
Autoconf upstream has this to say about the install-sh error: > And you should be aware that if a configure script > crashes with an error about not finding install-sh, this actually > means you need to add config.sub and config.guess to the source tree > as well. (A patch for that one is in the works. autoreconf --install > will correct the problem for packages that use automake, but not > otherwise.)
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=509275acfc734c578754f3f57f0c710e9b98329c has taken care of this issue...