x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I.. -DVERSION=\2.3.1+git\ -DPACKAGE_NAME=\pgl\ -DHAVE_ZLIB -DPIDFILE=\/var/run/pgld.pid\ -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c -o src/pgld.o src/pgld.c src/pgld.c: In function setipinfo: src/pgld.c:358:67: error: struct tcphdr has no member named source 358 | sprintf(src, %u.%u.%u.%u:%u,NIPQUAD(ip->saddr),ntohs(tcp->source)); | ^~ src/pgld.c:359:67: error: struct tcphdr has no member named dest ------------------------------------------------------------------- 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 <== Sun, 15 Mar 2020 11:38:50 +0000 emerge -qpvO net-firewall/pglinux [ebuild N ] net-firewall/pglinux-2.3.1_p20171006 USE="zlib -cron -dbus -logrotate -networkmanager -qt5"
Created attachment 619792 [details] emerge-info.txt
Created attachment 619794 [details] emerge-history.txt
Created attachment 619796 [details] environment
Created attachment 619798 [details] etc.portage.tbz2
Created attachment 619800 [details] logs.tbz2
Created attachment 619802 [details] net-firewall:pglinux-2.3.1_p20171006:20200315-130727.log
Created attachment 619804 [details] temp.tbz2
musl upstream has a FAQ entry specifically for this error: https://wiki.musl-libc.org/faq.html#Q:-Why-am-I-getting- Suggested workarounds are in the FAQ.
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.
tinderbox_musl has reproduced this issue with version 2.3.1_p20171006-r1 - Updating summary.