INSTALL: document shared library pinning for static builds
authorMatthias St. Pierre <matthias.st.pierre@ncp-e.com>
Wed, 17 May 2023 09:54:07 +0000 (11:54 +0200)
committerTomas Mraz <tomas@openssl.org>
Mon, 12 Jun 2023 06:33:00 +0000 (08:33 +0200)
commitce451fb86141fedad607bd68840639b06616047e
treeb79ca2634da49c3015f378b8821d4f1bb1c6b56b
parent959c150a1dcc4535c2d94ac6f3310566723911f1
INSTALL: document shared library pinning for static builds

The libcrypto library uses shared library pinning to prevent its
cleanup handlers from crashing at program termination because of a
premature unloading of the shared library.

However, shared library pinning is enabled also for static builds,
which may lead to surpising behaviour if libcrypto is linked
statically to a shared third-party library, because in this case
the third-party library gets pinned.

This surprising behaviour is caused by the fact that the `no-shared`
configure option does not imply `no-pinshared`. Since this quirk
can't be changed without potentially breaking existing code, we just
document it here and provide a workaround.

Fixes #20977

Reviewed-by: Todd Short <todd.short@me.com>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20985)
INSTALL.md