libtool: link: x86_64-gentoo-linux-musl-gcc -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -Wall -Wunused -Wl,-O1 -Wl,--as-needed -o .libs/mkrfc2734 mkrfc2734.o ../librom1394/.libs/librom1394.so -lraw1394 x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-libs/libavc1394-0.5.4-r2/work/libavc1394-0.5.4/test -I.. -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -Wall -Wunused -c /var/tmp/portage/sys-libs/libavc1394-0.5.4-r2/work/libavc1394-0.5.4/test/panelctl.c /var/tmp/portage/sys-libs/libavc1394-0.5.4-r2/work/libavc1394-0.5.4/test/panelctl.c:30:10: fatal error: argp.h: No such file or directory 30 | #include <argp.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 ] sys-libs/libavc1394-0.5.4-r2 [ebuild N ] sys-libs/libavc1394-0.5.4-r2
Created attachment 618640 [details] emerge-info.txt
Created attachment 618642 [details] emerge-history.txt
Created attachment 618644 [details] environment
Created attachment 618646 [details] etc.portage.tbz2
Created attachment 618648 [details] logs.tbz2
Created attachment 618650 [details] sys-libs:libavc1394-0.5.4-r2:20200313-165403.log
Created attachment 618652 [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.