[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
.so version numbers for dlopen'd objects
- To: <openldap-technical@openldap.org>
- Subject: .so version numbers for dlopen'd objects
- From: "Paul B. Henson" <henson@acm.org>
- Date: Tue, 22 May 2018 12:51:49 -0700
- Content-language: en-us
- Thread-index: AdPyBb6tBJ/yEHJvTGqUe8R+9WbRyg==
I'm trying to get the OpenBSD openldap port updated to use modules,
currently it just builds everything into a monolithic binary. They are
objecting to the existence of the version number in the shared objects for
the modules:
-rwxr-xr-x 1 henson henson 1773576 May 21 12:54 back_bdb-2.4.so.2.10.7
-rwxr-xr-x 1 henson henson 864 May 21 12:54 back_bdb.la
lrwxrwxrwx 1 henson henson 22 May 21 12:54 back_bdb.so ->
back_bdb-2.4.so.2.10.7
They say that shared objects which are intended to be dlopen'd, as opposed
to linked to, should not include version numbers, and it should look like:
-rwxr-xr-x 1 henson henson 1773576 May 21 12:54 back_bdb-2.4.so
-rwxr-xr-x 1 henson henson 864 May 21 12:54 back_bdb.la
What is the openldap developer perspective on this?
Thanks.