libcrypto++ (8.6.0-3+rpi1) bookworm-staging; urgency=medium
authorPeter Michael Green <plugwash@raspbian.org>
Sat, 19 Mar 2022 22:09:41 +0000 (22:09 +0000)
committerPeter Michael Green <plugwash@raspbian.org>
Sat, 19 Mar 2022 22:09:41 +0000 (22:09 +0000)
commitd6ca187e16e74d35c4afa72fbb7942b16356d33e
tree7a51a900163507c7292e7ae762d8f40b1fb0e5c9
parenta40a2d9fc05f555d054bcb946e0a29b0cde3d8ce
parent3d825e6ca09896dc71157a977f7a14ee649a24ce
libcrypto++ (8.6.0-3+rpi1) bookworm-staging; urgency=medium

  * Upload to raspbian despite detection of armv7 contaimination,
    investigation of the code shows that the armv7/neon code seems
    to be safely behind runtime CPU testection.
  * Pass -march=armv7+fp instead of -march=armv7 when building "armv4"
    assembler files. Despite the names these files only seem to be used
    on armv7.

[dgit import unpatched libcrypto++ 8.6.0-3+rpi1]
25 files changed:
debian/changelog
debian/clean
debian/control
debian/copyright
debian/cryptest.1
debian/fix_library_name.sh
debian/libcrypto++-dev.docs
debian/libcrypto++-dev.install
debian/libcrypto++-dev.links.in
debian/libcrypto++-doc.doc-base
debian/libcrypto++-doc.docs
debian/libcrypto++-doc.links
debian/libcrypto++-utils.install
debian/libcrypto++-utils.manpages
debian/libcrypto++8.install
debian/libcrypto++8.links.in
debian/not-installed
debian/patches/GNUmakefile_update.patch
debian/patches/armhf_FTBFS_fix.patch
debian/patches/fix_library_name.patch
debian/patches/series
debian/patches/use-fp-with-march.patch
debian/rules
debian/source/format
debian/watch