Discussion:
Error: bad immediate value for offset (4100)
(too old to reply)
Mathieu Malaterre
2024-01-12 10:40:01 UTC
Permalink
[CC me please]

Dear ARM porters,

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 ?

Thanks !
Emanuele Rocca
2024-01-12 15:50:02 UTC
Permalink
Hi Mathieu!
Post by Mathieu Malaterre
* 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.
Peter Green
2024-06-19 21:20:02 UTC
Permalink
Post by Emanuele Rocca
Hi Mathieu!
Post by Mathieu Malaterre
* 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 ?
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.
Loading...