In file included from pppoe.h:94, from plugin.c:29: /usr/include/netinet/if_ether.h:113:8: error: redefinition of struct ethhdr 113 | struct ethhdr { | ^~~~~~ In file included from pppoe.h:84, ------------------------------------------------------------------- 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-1.41.1 * The following VMs are available for generation-2: repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sat, 14 Mar 2020 16:44:09 +0000 emerge -qpvO net-dialup/ppp [ebuild N ] net-dialup/ppp-2.4.8 USE="ipv6 pam -activefilter -atm -dhcp -eap-tls -gtk -libressl -radius"
Created attachment 619108 [details] emerge-info.txt
Created attachment 619110 [details] emerge-history.txt
Created attachment 619112 [details] environment
Created attachment 619114 [details] etc.portage.tbz2
Created attachment 619116 [details] net-dialup:ppp-2.4.8:20200314-175508.log
Created attachment 619118 [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.
