CC timer.lo CC signal.lo signal.c:90:4: error: SIGCLD undeclared here (not in a function); did you mean SIGCHLD? 90 | { SIGCLD, CLD }, | ^~~~~~ | SIGCHLD ------------------------------------------------------------------- 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 08:14:23 +0000 emerge -qpvO sys-libs/libnih [ebuild N ] sys-libs/libnih-1.0.3-r3 USE="dbus nls (split-usr) threads -static-libs"
Created attachment 619664 [details] emerge-info.txt
Created attachment 619666 [details] emerge-history.txt
Created attachment 619668 [details] environment
Created attachment 619670 [details] etc.portage.tbz2
Created attachment 619672 [details] logs.tbz2
Created attachment 619674 [details] sys-libs:libnih-1.0.3-r3:20200315-094935.log
Created attachment 619676 [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.
