Rebuilding libp11 after upgrading to openssl-3.1 results in libp11's soname changing from libp11.so.3 to libp11.so.2. This is caused by this buggy configure logic: > # we need to set our soversion based on openssl's soversion to avoid > # issues with applications linking to new openssl, old libp11, and vice versa > case "`$PKG_CONFIG --modversion --silence-errors libcrypto || \ > $PKG_CONFIG --modversion openssl`" in > 3.0.*) # Predicted engines directory prefix for OpenSSL 3.x > LIBP11_LT_OLDEST="3" > debian_ssl_prefix="openssl-3.0.0";; > 1.1.*) # Predicted engines directory prefix for OpenSSL 1.1.x > LIBP11_LT_OLDEST="3" > debian_ssl_prefix="openssl-1.1.0";; > 1.0.*) # Engines directory prefix for OpenSSL 1.0.x > LIBP11_LT_OLDEST="2" > debian_ssl_prefix="openssl-1.0.0";; > *) # Engines directory prefix for OpenSSL 0.9.x > LIBP11_LT_OLDEST="2" > debian_ssl_prefix="ssl";; > esac
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9e38d26b4c391c4431a98cd9cb550c0247bdd00 commit a9e38d26b4c391c4431a98cd9cb550c0247bdd00 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2023-07-10 22:47:42 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2023-07-10 22:47:42 +0000 dev-libs/libp11: fix openssl-3.1 detection Closes: https://bugs.gentoo.org/910203 Signed-off-by: Mike Gilbert <floppym@gentoo.org> .../libp11/files/libp11-0.4.12-openssl-3.1.patch | 25 ++++++++++++++++++++++ ...11-0.4.12-r2.ebuild => libp11-0.4.12-r3.ebuild} | 18 +++++++++++++--- 2 files changed, 40 insertions(+), 3 deletions(-)
