* ERROR: net-fs/openafs-1.8.6::gentoo failed (prepare phase): * Failed Running autoconf ! * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-libressl-20201010-201503 ------------------------------------------------------------------- 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 * The following VMs are available for generation-2: 1) IcedTea JDK 3.16.0 [icedtea-bin-8] 2) JamVM JDK 2.0.0 [jamvm] 3) OpenJDK 8.265_p01 [openjdk-8] *) AdoptOpenJDK 8.265_p01 [openjdk-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 [2] jamvm [3] openjdk-8 [4] 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 Mon Oct 19 04:05:16 AM UTC 2020 /var/db/repos/libressl Sun Oct 18 04:35:14 PM UTC 2020 emerge -qpvO net-fs/openafs [ebuild N ] net-fs/openafs-1.8.6 USE="modules namei ncurses pthreaded-ubik supergroups -apidoc -bitmap-later -debug -doc -fuse -kauth -kerberos -perl -tsm -ubik-read-while-write"
Created attachment 666800 [details] emerge-info.txt
Created attachment 666803 [details] autoconf.out
Created attachment 666806 [details] emerge-history.txt
Created attachment 666809 [details] environment
Created attachment 666812 [details] etc.portage.tbz2
Created attachment 666815 [details] logs.tbz2
Created attachment 666818 [details] net-fs:openafs-1.8.6:20201019-055732.log
Created attachment 666821 [details] temp.tbz2
Hi! As far as I understand, this bug is a part of autoconf-2.70 testing. Though 2.70_beta2-r1 is no longer in the tree and I can't reproduce this problem with autoconf-2.70_beta3-r1: it runs successfully with the same USE flags. Please test again with >=autoconf-2.70_beta3-r1. Thanks.
