Hi Everyone,
The patch to work around the failed compile is located at
https://github.com/weidai11/cryptopp/issues/1094#issuecomment-1035656572
. The patch is against Crypto++ 8.6.
The patch was tested in a Debian Unstable QEMU/Chroot for armel and
armhf. It tested Ok.
The changes in the diff
Hi Everyone,
I think this is a GCC or Debian bug. Here is my reasoning.
Developers are responsible to declare the ISA they are using through
options. In our case, we are using armv4 and armv7, so we let the
compiler know via -march=armv7-a. That's where a developer's
responsibility ends. We are
I opened this for the GCC folks:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455. I'm not sure if
they are aware things no longer work.
Jeff
Hi Everyone,
My apologies for the late reply.
SL > There are various ways to reconcile this incompatibility between
SL > build options, but given this is armhf which is guaranteed to have
SL > floating-point support, I think the simplest may be as in the
SL > attached patch, which adjusts to
Control: tags -1 +confirmed
Control: forwarded -1 https://github.com/weidai11/cryptopp/issues/1094
Hi Steve,
On Mon, Dec 20, 2021 at 1:03 AM Steve Langasek
wrote:
> Libcrypto++ is failing to build on armhf because gcc there defaults to an
> implied -mfloat-abi=hard, which conflicts with
Package: libcrypto++
Version: 8.6.0-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Hi Laszlo,
Libcrypto++ is failing to build on armhf because gcc there defaults to an
implied -mfloat-abi=hard, which conflicts with -march=armv7-a
6 matches
Mail list logo
