checking for EVENT... yes checking for EVENT_PTHREADS... no configure: error: libevent_pthreads version 2.0.21 or greater not found. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-p2p/bitcoind-0.21.0/work/bitcoin-95ea54ba089610019a74c1176a2c7c0dba144b1c/config.log * ERROR: net-p2p/bitcoind-0.21.0::gentoo failed (configure phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-j3-20210804-091539 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * clang version 12.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.1 Python 3.9.6 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.54.0 * The following VMs are available for generation-2: *) AdoptOpenJDK JRE 8.292_p10 [openjdk-jre-bin-8] Available Java Virtual Machines: [1] openjdk-jre-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit 48adc8c4df0d96a8305ce0aa6970d687f67d4750 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sun Aug 8 08:07:05 2021 +0000 2021-08-08 08:07:03 UTC emerge -qpvO net-p2p/bitcoind [ebuild N ] net-p2p/bitcoind-0.21.0 USE="asm sqlite wallet -examples -knots -system-leveldb -test -upnp -zeromq"
Created attachment 731374 [details] emerge-info.txt
Created attachment 731377 [details] emerge-history.txt
Created attachment 731380 [details] environment
Created attachment 731383 [details] etc.portage.tar.bz2
Created attachment 731386 [details] logs.tar.bz2
Created attachment 731389 [details] net-p2p:bitcoind-0.21.0:20210808-083438.log
Created attachment 731392 [details] temp.tar.bz2
Would be nice if something indicated what is unusual about this test system?
2021-08-04T09:22:35 >>> sys-libs/glibc-2.34
Cannot reproduce. From the logs, it looks most likely a miscompile of libevent, but I couldn't reproduce that either.
(In reply to Luke-Jr from comment #10) > Cannot reproduce. From the logs, it looks most likely a miscompile of > libevent, but I couldn't reproduce that either. You tried with glibc-2.34?
(In reply to Sam James from comment #11) > (In reply to Luke-Jr from comment #10) > > Cannot reproduce. From the logs, it looks most likely a miscompile of > > libevent, but I couldn't reproduce that either. > > You tried with glibc-2.34? Yes, upgraded the latest stage3 in a fresh chroot
*** Bug 807885 has been marked as a duplicate of this bug. ***
(In reply to Luke-Jr from comment #12) > (In reply to Sam James from comment #11) > > (In reply to Luke-Jr from comment #10) > > > Cannot reproduce. From the logs, it looks most likely a miscompile of > > > libevent, but I couldn't reproduce that either. > > > > You tried with glibc-2.34? > > Yes, upgraded the latest stage3 in a fresh chroot Interesting, thanks!
(In reply to Luke-Jr from comment #12) > (In reply to Sam James from comment #11) > > (In reply to Luke-Jr from comment #10) > > > Cannot reproduce. From the logs, it looks most likely a miscompile of > > > libevent, but I couldn't reproduce that either. > > > > You tried with glibc-2.34? > > Yes, upgraded the latest stage3 in a fresh chroot OK no duplicates, so let's assume this was cosmic radiation. :) If the problem reappears, feel free to reopen.
I can reproduce this bug after disabling the "threads" USE flag for the package dev-libs/libevent
failed at ~tinderbox/img/17.1_desktop_gnome_systemd-j4-20230210-10002 too
