I recently switched from netatalk3 to samba413 (for use as a time machine share) and I find that /usr/local/lib/nss_wins.so.1 is linked against many shared libraries in /usr/local/lib/samba4/private but is not linked with -rpath/LD_RUN_PATH: zinc 24 @ ldd /usr/local/lib/nss_wins.so.1 | fgrep found | head -3 libwinbind-client-samba4.so => not found (0) libreplace-samba4.so => not found (0) libutil-setid-samba4.so => not found (0) I have a cron job that looks for a reports binaries and shared libraries that have this problem. Clearly samba works this way (presumably all binaries that use nss_wins.so.1 have the correct -rpath/LD_RUN_PATH) but is it unreasonable for me to have the expectation that nss_wins.so.1 to by itself be able to find it's dependent shared libraries?
I've just checked and indeed, some libs are not linked in properly. Haven't figured out yet, why. From other side I'm a bit surprised that anyone is using this module, TBH. It was added while ago for completeness, but IMHO, is pretty useless by itself, as it just allows to use NETBIOS host names next to the normal DNS names. In 2021 that has very limited use, if any...
(In reply to Timur I. Bakeyev from comment #1) I can't convince myself there is anything that even uses nss_wins.so.1! Certainly running ldd on the files that are installed by samba413 doesn't show any references.
(In reply to Timur I. Bakeyev from comment #1) (To be clear my only interest is that the port not install any binaries or shared libraries that ldd reports "not found" when checked)