In file included from kupdate.c:32: kupdate.c: In function _kupdate_get_interval: kupdate.c:191:23: error: HZ undeclared (first use in this function) 191 | *interval, 5*HZ); | ^~ bug.h:57:33: note: in definition of macro INFO ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200311-204810 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-9.2.0 * [2] 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-bin-1.41.1 [2] rust-1.41.1 * The following VMs are available for generation-2: repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sun, 15 Mar 2020 22:38:22 +0000 emerge -qpvO sys-block/noflushd [ebuild N ] sys-block/noflushd-2.8
Created attachment 620200 [details] emerge-info.txt
Created attachment 620202 [details] emerge-history.txt
Created attachment 620204 [details] environment
Created attachment 620206 [details] etc.portage.tbz2
Created attachment 620208 [details] logs.tbz2
Created attachment 620210 [details] sys-block:noflushd-2.8:20200315-231209.log
Created attachment 620212 [details] temp.tbz2
The first attempt to tinderbox a musl image failed at all. I'll mass close therefore all filed bug reports of the last days related to this tinderbox image. Please feel free to re-open if you think that the bug is real in musl and not fixed by the musl overlay.
tinderbox_musl has reproduced this issue with version 2.8-r1 - Updating summary.
Package removed.
