On Tue, Sep 29, 2020 at 7:29 AM Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
> And we are by pushing glibc2.32 late in groovy we are forcing everything that
> is left to resolve the same now. I'm not sure should glibc provide a compat
> path - I assume this was made so that every project has to make a concious
> switch?
Others (I checked Fedora, and I think gentoo did it too) did the
switch years ago (circa 2018). They have a master bug[1] which might
be worth checking if someone is looking for patches.
> Note, in most cases this include path should be covered by libtirpc pkg-config.
> # pkg-config --cflags libtirpc
> -I/usr/include/tirpc
> But e.g. in the case of open-vm-tools that seems not to be propagated to all
> toolchain calls :-/
I briefly tried building squid's NIS auth helper with tirpc when
trying to sort out its ftbfs[2]. It worked, but for reasons outlined
in the bug[2] and the WIP branch[3] which I didn't propose, I decided
to drop the NIS auth helper. Other than some annoying autoconf issues,
it seemed to work just fine, but I didn't have a real NIS domain to
test.
Of note is that the final binary wasn't directly linked with tirpc,
but pulled it in via libnsl.
1. https://bugzilla.redhat.com/show_bug.cgi?id=1531540
2. https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1895694
3. https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+ref/groovy-squid-use-tirpc
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
