On 12/01/2024 15:49, Emanuele Rocca wrote:
Hi Mathieu!
On 2024-01-12 11:33, Mathieu Malaterre wrote:
Could someone please confirm what I see on the armel/buildd:
* https://buildd.debian.org/status/fetch.php?pkg=dcmtk&arch=armel&ver=3.6.8-2&stamp=1705054390&raw=0
Is this a 32bits/limited RAM issue ? Is there a way to fix the symptoms ?
This seems to be caused by stack-clash-protection. Try with:
ifeq ($(DEB_TARGET_ARCH),armel)
export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash
else
Interestingly, the problem does not affect armhf.
FWIW, while it doesn't affect Debian armhf, it does affect raspbian.
This suggests that it is either a difference between different arm
CPU versions, or a difference between traditional arm (used by Debian
armel and Raspbian) and thumb2 (used by Debian armhf) code generation.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)