On 12 Oct, Don Lewis wrote: > Prior to the OpenSSL 1.1.1 import, the base OpenSSL library was > /usr/lib/libssl.so.8. The security/openssl port (1.0.2p) installed > ${LOCALBASE}/lib/ilbssl.so.9 and the security/openssl-devel port > (1.1.0i) installed ${LOCALBASE}/lib/libssl.so.11. After the import, the > base OpenSSL library is /usr/lib/libssl.so.9. Now if you build ports > with DEFAULT_VERSIONS+=ssl=openssl, the library that actually gets used > is ambiguous because there are now two different versions of libssl.so > (1.0.2p and 1.1.1) with the same shared library version number. > > I stumbled across this when debugging a virtualbox-ose configure > failure. The test executable was linked to the ports version of > libssl.so but rtld chose the base libssl.so at run time. It looks to me like the base libssl.so version needs to get moved to a value that doesn't collide with ports, perhaps 12. These are the library version numbers currently used by the various ssl ports: boringssl 1 openssl 9 openssl-devel 10 openssl111 11 libressl 43 libressl-devel 44Received on Sun Oct 14 2018 - 04:00:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:18 UTC