https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219606
--- Comment #9 from Mark Millard <mar...@dsl-only.net> --- (In reply to Ed Maste from comment #8) > [Ed's description of shared library version handling] Yep, that is expected. I've tried to remember how or when I ran into a generic reference to a: /usr/lib/lib<something>.so or: /lib/lib<something>.so or some such being used to find a library when it was a symbolic link but I've not managed to remember anything. It was not recently --and not even necessarily under FreeBSD since I'm remembering so little. I just end up with a "careful of assumptions" reaction from some past problem that I ran into. All I can say that that I'm pretty sure I've run into the issue where something actually used a generic .so link directly and found and used directly what it pointed to instead of an original binding. (May be it was a fail-over for the original binding not being available to find any more?) This can be translated to: if things still seem to not be working as expected, see if you can check if the link is in direct use from a context where that would not work. A "yes" to that would mean another problem is involved someplace. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"