summaryrefslogtreecommitdiff
path: root/meta/recipes-extended/acpica
diff options
context:
space:
mode:
authorJussi Kukkonen <jussi.kukkonen@intel.com>2017-04-20 16:32:19 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-04-21 08:22:03 +0100
commit1b430eef7131876bc735c22d66358379b0516821 (patch)
treefcc467adcae501c41714ad68446ab32cdf380061 /meta/recipes-extended/acpica
parenteb4fee616287ae731f7af52e0fe5fc81f2eea2c0 (diff)
downloadopenembedded-core-1b430eef7131876bc735c22d66358379b0516821.tar.gz
openembedded-core-1b430eef7131876bc735c22d66358379b0516821.tar.bz2
openembedded-core-1b430eef7131876bc735c22d66358379b0516821.zip
openssl: Bump SONAME to match the ABI
Commit 7933fbbc637 "Security fix Drown via 1.0.2g update" included a version-script change from Debian that was an ABI change. It did not include the soname change that Debian did so we have been calling our ABI 1.0.0 but it really matches what others call 1.0.2. Bump SONAME to match the ABI. In practice this changes both libcrypto and libssl sonames from 1.0.0 to 1.0.2. For background: Upstream does not do sonames so these are set by distros. In this case the ABI changes based on a build time configuration! Debian took the ABI changing configuration and bumped soname but e.g. Ubuntu kept the deprecated API and just made it not work, keeping soname. So both have same version of openssl but support different ABI (and expose different SONAME). Fixes [YOCTO #11396]. Thanks to Alexander Larsson et al for detective work. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-extended/acpica')
0 files changed, 0 insertions, 0 deletions