Hi Mathieu et al., it seems that the stack problem is limited to the "drttest" tool, which is not really needed for a Linux distribution like Debian.
Anyway, in the meantime, I have revised the implementation of this test tool to avoid the creation of huge data structures on the stack. See this commit: https://git.dcmtk.org/?p=dcmtk.git;a=commit;h=bdc18c85b7fca130464dd745ea3efef3c9b8b94e It's up to you whether you switch to this implementation for the "experimental" 3.6.8 package or not. For 3.6.7 ("unstable" and "testing"), there seems to be another solution. Regards, Jörg ------------------------------------------------------------- Subject: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100) Date: Sunday, January 14, 2024, 11:24:06 AM CET From: Mathieu Malaterre <ma...@debian.org> To: Emanuele Rocca, 1060...@bugs.debian.org Control: fixed -1 3.6.8-3 On Sat, Jan 13, 2024 at 9:42 PM Emanuele Rocca <e...@debian.org> wrote: > > Control: user -1 debian-...@lists.debian.org > Control: usertag -1 + 32bit-stackclash > > Hi, > > On Fri, Jan 05, 2024 at 11:45:28PM +0100, Sebastian Ramacher wrote: > > /tmp/ccm0eYhx.s: Assembler messages: > > /tmp/ccm0eYhx.s:537: Error: bad immediate value for offset (4100) > > This is caused by stack-clash-protection on armel and a workaround is in > version 3.6.8-3 currently in experimental, see: > https://tracker.debian.org/news/1494233/accepted-dcmtk-368-3-source-into-experimental/ > > We should downgrade the severity to minor once the fix enters unstable, but > keep the bug open as this seems to be an interesting case of > stack-clash-protection malfunctioning on 32bit arm to further look into. Bit lost here... I do not see the bug reported against GCC-13 package. In the end do you want me to upload a patched 3.6.7 or is it ok to wait for transition ? Thanks! ------------------------------------------------------------- -- Dr. Joerg Riesmeier, Etzhorner Weg 19, 26125 Oldenburg, Germany E-Mail: di...@jriesmeier.com, Homepage: www.jriesmeier.com
