Note to self on the bearssl thing:

The bearssl autopkgtests create a binary that is linked against
libbearssl *and* lib25519, yet the bearssl autopkgtests didn't warn when
it was run against glibc 2.41-9ubuntu1 (which does not have GCS enable).

It actually makes sense: executables have crt1.o linked in. The old one
didn't have the GCS bit, so that propagated into the final executable.
The linker only complains about shared libs if the executable itself has
GCS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2121033

Title:
  lib25519 doesn't expose GCS attribute on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2121033/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to