* Running eautoreconf in '/var/tmp/portage/x11-misc/bbdate-0.2.4-r3/work/bbdate-0.2.4' ... * Running 'aclocal --system-acdir=/var/tmp/portage/x11-misc/bbdate-0.2.4-r3/temp/aclocal' ... [ ok ] * Running 'autoconf --force' ... [ !! ] * Failed running 'autoconf'! * * Include in your bug report the contents of: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-20231224-184505 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 17.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/17/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/17 17.0.6 Python 3.11.7 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.74.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 17.0.8.1_p1 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.1_p12 [openjdk-bin-21] 3) Eclipse Temurin JDK 8.382_p05 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 [3] openjdk-bin-21 system-vm The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): go version go1.21.5 linux/amd64 HEAD of ::gentoo commit 5f2f79e6c633e8cc92b8beed9337432b59093ca6 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Dec 26 21:46:59 2023 +0000 2023-12-26 21:46:59 UTC emerge -qpvO x11-misc/bbdate [ebuild N ] x11-misc/bbdate-0.2.4-r3
Created attachment 880675 [details] emerge-info.txt
Created attachment 880676 [details] emerge-history.txt
Created attachment 880677 [details] environment
Created attachment 880678 [details] etc.clang.tar.xz
Created attachment 880679 [details] etc.portage.tar.xz
Created attachment 880680 [details] qlist-info.txt.xz
Created attachment 880681 [details] temp.tar.xz
Created attachment 880682 [details] x11-misc:bbdate-0.2.4-r3:20231226-230419.log
*** This bug has been marked as a duplicate of bug 920822 ***