x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I../include -I../Misc -O2 -DLINUX -Wall -pedantic -funsigned-char -DMOD_CLNT_BIND_REUSE -DMOD_CLNT_CONFIRM -std=c99 -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c -o libLowLevel_a-interface.o test -f interface.c || echo ./interface.c In file included from interface.c:40: ethtool-local.h:25:9: error: unknown type name __uint32_t 25 | typedef __uint32_t u32; | ^~~~~~~~~~ ethtool-local.h:26:9: error: unknown type name __uint16_t ------------------------------------------------------------------- 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: clang version 10.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/10/bin llvm: 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 14:38:45 +0000 emerge -qpvO net-misc/dibbler [ebuild N ] net-misc/dibbler-1.0.1-r2 USE="-doc -resolvconf"
Created attachment 618478 [details] emerge-info.txt
Created attachment 618480 [details] emerge-history.txt
Created attachment 618482 [details] environment
Created attachment 618484 [details] etc.portage.tbz2
Created attachment 618486 [details] logs.tbz2
Created attachment 618488 [details] net-misc:dibbler-1.0.1-r2:20200313-153427.log
Created attachment 618490 [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.
This error has been fixed in a patch in ::musl overlay, and since been included upstream in commit 8455dcb. To date, a release hasn't been cut, so we'll have to carry the patch for a little while longer. *** This bug has been marked as a duplicate of bug 551818 ***