At Tue, 22 May 2018 17:20:57 -0700 "Paul B. Henson" <henson(a)acm.org>
> From: Robert Heller
> Sent: Tuesday, May 22, 2018 1:16 PM
> (specificly Tcl extensions). If using libtool, it *should* create
> for the .so file without the version numbers like this:
Yes, currently it both creates a .so.x.y file as well as a symbolic link
from just .so, the assertion from OpenBSD is that for this use case there
should only be the .so.
You can suppress the version numbers with the "-avoid-version" LDFLAGS option
(I need to do this with the MS-Windows cross-build).
> In my case, the shared library is *both* a dlopen'ed tcl extension and can
> also be linked to by a C++ program. This is under Linux, but I do the
> under MacOSX (which is an OpenBSD variant under-the-hood).
OS X is actually based off of FreeBSD :). But all of the BSD's cross
pollinate to some extent.
In this case, it is only a dynamically loaded module, I do not believe it is
suitable or there would be a use case to link to it directly from an
application. I don't really care myself, but it is one of the stall points
keeping my changes from getting incorporated so I need to sort it out.
Robert Heller -- 978-544-6933
Deepwoods Software -- Custom Software Services
-- Linux Administration Services
heller(a)deepsoft.com -- Webhosting Services