x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DREVISION=\-release\ -DTHREADING_SUPPORT -DINOTIFY_SUPPORT -DBACKTRACE_SUPPORT -DCAPABILITIES_SUPPORT -DSECCOMP_SUPPORT -DGETMNTENT_SUPPORT -DHL_LOCKS -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c -o clsync-calc.o test -f calc.c || echo ./calc.c In file included from calc.c:20: common.h:61:10: fatal error: fts.h: No such file or directory 61 | #include <fts.h> | ^~~~~~~ compilation terminated. ------------------------------------------------------------------- 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 * 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) * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Fri, 13 Mar 2020 15:38:54 +0000 [ebuild N ] app-admin/clsync-0.4.2 USE="caps highload-locks inotify seccomp -cgroups (-cluster) -control-socket -debug -extra-debug -extra-hardened -gio -hardened (-mhash) -namespaces" [ebuild N ] app-admin/clsync-0.4.2 USE="caps highload-locks inotify seccomp -cgroups (-cluster) -control-socket -debug -extra-debug -extra-hardened -gio -hardened (-mhash) -namespaces"
Created attachment 618654 [details] emerge-info.txt
Created attachment 618656 [details] app-admin:clsync-0.4.2:20200313-170334.log
Created attachment 618658 [details] emerge-history.txt
Created attachment 618660 [details] environment
Created attachment 618662 [details] etc.portage.tbz2
Created attachment 618664 [details] logs.tbz2
Created attachment 618666 [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.