x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I. -I. -O2 -g -Wall -D_GNU_SOURCE -DP_SERIES -Isrc -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c src/ehca_umain.c -fPIC -DPIC -o .libs/ehca_umain.o In file included from src/ehca_umain.c:45: src/ehca_uclasses.h:48:10: fatal error: sys/queue.h: No such file or directory 48 | #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 * [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 <== Mon, 16 Mar 2020 04:38:59 +0000 emerge -qpvO sys-fabric/libehca [ebuild N ] sys-fabric/libehca-1.2.2-r3
Created attachment 620374 [details] emerge-info.txt
Created attachment 620376 [details] emerge-history.txt
Created attachment 620378 [details] environment
Created attachment 620380 [details] etc.portage.tbz2
Created attachment 620382 [details] logs.tbz2
Created attachment 620384 [details] sys-fabric:libehca-1.2.2-r3:20200316-060240.log
Created attachment 620386 [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.
