But we'd want to ask Debian to take the same, for that we need to find which-of/if the flags above are causing this.
Likely strl* functions are not meant to be exported as they are part of libbsd-dev see https://manpages.ubuntu.com/manpages/jammy/man3/strlcpy.3bsd.html and not of e.g. in this case libqb.
So maybe the compiler flags now hides these not meant to be exported symbols that are actually in libbsd0?
Once sufficiently understood consider providing a PR on Salsa to avoid this from ever affecting Debian (and link it from here)
New flags between /launchpadlibra rian.net/ 678368627/ buildlog_ ubuntu- mantic- amd64.libqb_ 2.0.8-1_ BUILDING. txt.gz /launchpadlibra rian.net/ 685152138/ buildlog_ ubuntu- mantic- amd64.libqb_ 2.0.8-1_ BUILDING. txt.gz clash-protectio n -fcf-protection
https:/
and
https:/
are: -fstack-
That is part of the Ubuntu hardening.
Most likely the "fix" is just the same as in launchpadlibrar ian.net/ 686836480/ gpsd_3. 25-2ubuntu1_ 3.25-2ubuntu2. diff.gz
http://
But we'd want to ask Debian to take the same, for that we need to find which-of/if the flags above are causing this.
Likely strl* functions are not meant to be exported as they are part of libbsd-dev see https:/ /manpages. ubuntu. com/manpages/ jammy/man3/ strlcpy. 3bsd.html and not of e.g. in this case libqb.
So maybe the compiler flags now hides these not meant to be exported symbols that are actually in libbsd0?
Once sufficiently understood consider providing a PR on Salsa to avoid this from ever affecting Debian (and link it from here)