*** dnotify. If you are already running 2.4.19 or later please *** report this as a bug to <oskar@osk.mine.nu>. configure: error: kernel has fl_owner bug !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-apps/dnotify-0.18.0/work/dnotify-0.18.0/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200316-165821 ------------------------------------------------------------------- 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.41.1 * timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Sat Mar 21 17:38:44 UTC 2020 /var/db/repos/musl Sat Mar 21 03:09:12 UTC 2020 emerge -qpvO sys-apps/dnotify [ebuild N ] sys-apps/dnotify-0.18.0 USE="nls"
Created attachment 623978 [details] emerge-info.txt
Created attachment 623980 [details] emerge-history.txt
Created attachment 623982 [details] environment
Created attachment 623984 [details] etc.portage.tbz2
Created attachment 623986 [details] logs.tbz2
Created attachment 623988 [details] sys-apps:dnotify-0.18.0:20200321-190501.log
Created attachment 623990 [details] temp.tbz2
tinderbox_musl has reproduced this issue with version 0.18.0-r1 - Updating summary.