At Sat, 16 Mar 2024 22:21:21 +0000, Taylor R Campbell <campbell+netbsd-tech-userle...@mumble.net> wrote: Subject: Checking library symbols > > So far this is experimental -- I only tried it with openssl libcrypto > to verify another experiment with renaming sha2 symbols. It's limited > to shared libraries, not static libraries, for now. In practice we > might require more mechanism to handle MD variation in the set of > defined symbols (especially with libm), and we might encounter other > problems I haven't foreseen if we try to apply this to more libraries, > but I thought I'd share a first draft.
It seems it can cause builds with non-default MK* options such as
MKINET6=no to fail.
See my post from today on current-users.
The particular case I ran into for libpcap would seem to be a design
flaw in libpcap's API, though I'm not so familiar with libpcap that I
can be sure.
--
Greg A. Woods <gwo...@acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <wo...@robohack.ca>
Planix, Inc. <wo...@planix.com> Avoncote Farms <wo...@avoncote.ca>
pgpqO7LSYBzdJ.pgp
Description: OpenPGP Digital Signature
