114 | struct gaih_addrtuple **pat, | ^~~~~~~~~~~~~~ nss-myhostname.c:112:17: error: conflicting types for _nss_myhostname_gethostbyname4_r 112 | enum nss_status _nss_myhostname_gethostbyname4_r( | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ nss-myhostname.c:68:17: note: previous declaration of _nss_myhostname_gethostbyname4_r was here ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200328-141627 ------------------------------------------------------------------- gcc-config -l: [1] 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.42.0 * The following VMs are available for generation-2: Available Java Virtual Machines: (none found) timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Sun Apr 5 03:07:54 UTC 2020 /var/db/repos/musl Sat Apr 4 03:02:24 UTC 2020 emerge -qpvO sys-auth/nss-myhostname [ebuild N ] sys-auth/nss-myhostname-0.3
Created attachment 630346 [details] emerge-info.txt
Created attachment 630348 [details] emerge-history.txt
Created attachment 630350 [details] environment
Created attachment 630352 [details] etc.portage.tbz2
Created attachment 630354 [details] logs.tbz2
Created attachment 630356 [details] sys-auth:nss-myhostname-0.3:20200405-060449.log
Created attachment 630358 [details] temp.tbz2
Does musl actually use NSS?
(In reply to Michał Górny from comment #8) > Does musl actually use NSS? no
(In reply to Sam James from comment #9) > (In reply to Michał Górny from comment #8) > > Does musl actually use NSS? > > no I think, rightly, that this can be fixed with some form of mask, yes?
Yes, I suppose all NSS providers should be masked in musl profiles.
(In reply to Michał Górny from comment #11) > Yes, I suppose all NSS providers should be masked in musl profiles. I'll have a look through the repo, and suggest some masks to musl@ via a PR or such-like. Then this kinda thing shouldn't crop up again.
(In reply to Michael 'veremitz' Everitt from comment #12) > (In reply to Michał Górny from comment #11) > > Yes, I suppose all NSS providers should be masked in musl profiles. > > I'll have a look through the repo, and suggest some masks to musl@ via a PR > or such-like. Then this kinda thing shouldn't crop up again. This is already fixed in the overlay.