| ^~~~~~~ /var/tmp/portage/dev-libs/dbus-c++-0.9.0-r3/work/libdbus-c++-0.9.0/src/eventloop.cpp: In constructor DBus::DefaultMutex::DefaultMutex(bool): /var/tmp/portage/dev-libs/dbus-c++-0.9.0-r3/work/libdbus-c++-0.9.0/src/eventloop.cpp:88:32: error: PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP was not declared in this scope; did you mean PTHREAD_MUTEX_INITIALIZER? 88 | pthread_mutex_t recmutex = PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | PTHREAD_MUTEX_INITIALIZER ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl_hardened-20200328-201618 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-gentoo-linux-musl-9.3.0 * clang version 10.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.42.0 * timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Tue Mar 31 19:13:24 UTC 2020 /var/db/repos/musl Fri Mar 27 00:25:27 UTC 2020 emerge -qpvO dev-libs/dbus-c++ [ebuild N ] dev-libs/dbus-c++-0.9.0-r3 USE="-doc -ecore -glib -static-libs -test"
Created attachment 628184 [details] emerge-info.txt
Created attachment 628186 [details] dev-libs:dbus-c++-0.9.0-r3:20200331-215204.log
Created attachment 628188 [details] emerge-history.txt
Created attachment 628190 [details] environment
Created attachment 628192 [details] etc.portage.tbz2
Created attachment 628194 [details] logs.tbz2
Created attachment 628196 [details] temp.tbz2
tinderbox_musl has reproduced this issue with version 0.9.0-r4 - Updating summary.
tinderbox_musl has reproduced this issue with version 0.9.0-r5 - Updating summary.