make: Entering directory /var/tmp/portage/dev-util/dropwatch-1.4_p20150706/work/dropwatch-1.4_p20150706/src x86_64-gentoo-linux-musl-gcc -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -g -Wall -I/usr/include/libnl3 -D_GNU_SOURCE -c -o main.o main.c main.c:34:10: fatal error: sys/queue.h: No such file or directory 34 | #include <sys/queue.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 * 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 <== Thu, 12 Mar 2020 23:38:53 +0000 emerge -qpvO dev-util/dropwatch [ebuild N ] dev-util/dropwatch-1.4_p20150706
Created attachment 618334 [details] emerge-info.txt
Created attachment 618336 [details] dev-util:dropwatch-1.4_p20150706:20200313-025002.log
Created attachment 618338 [details] emerge-history.txt
Created attachment 618340 [details] environment
Created attachment 618342 [details] etc.portage.tbz2
Created attachment 618344 [details] temp.tbz2
Quoting @Kumba from https://bugs.gentoo.org/712656#c8 > This is fixable by adding an elibc_musl USE dep to pull in > sys-libs/queue-standalone. > >musl upstream has a FAQ entry specifically for this error: >https://wiki.musl-libc.org/faq.html#Q:-Why-is-%3Ccode%3Esys/queue.h%3C/code%3E-not-included?
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.
