libtool: compile: x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -DAUTOSHARE=/usr/share/LibDsk -Wall -DNOTWINDLL -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c drvposix.c -fPIC -DPIC -o .libs/drvposix.o In file included from drvposix.c:31: drvposix.h:41:11: error: conflicting types for posix_close 41 | dsk_err_t posix_close(DSK_DRIVER *self); | ^~~~~~~~~~~ In file included from drvi.h:33, ------------------------------------------------------------------- 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-1.41.1 * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Fri, 13 Mar 2020 23:39:58 +0000 emerge -qpvO app-emulation/libdsk [ebuild N ] app-emulation/libdsk-1.5.8 USE="-doc"
Created attachment 618732 [details] emerge-info.txt
Created attachment 618734 [details] app-emulation:libdsk-1.5.8:20200314-022650.log
Created attachment 618736 [details] emerge-history.txt
Created attachment 618738 [details] environment
Created attachment 618740 [details] etc.portage.tbz2
Created attachment 618742 [details] logs.tbz2
Created attachment 618744 [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 1.5.18 - Updating summary.