info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Error: bad immediate value for offset (4100)
6 views
Skip to first unread message
Mathieu Malaterre
Jan 12, 2024, 5:40:04 AMJan 12
to
[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 !
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
Jan 12, 2024, 10:50:04 AMJan 12
to
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.
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 ?
ifeq ($(DEB_TARGET_ARCH),armel)
export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash
else
Interestingly, the problem does not affect armhf.
0 new messages