Bug#871514: clamav: FTBFS on mips64el

2017-08-23 Thread James Cowgill
Control: forcemerge -1 872438 Hi, Just a brief update on this bug. Unfortunately there is still no "good" fix. As I have written in a few places now, the bug occurs on mips64el where a "small" variable gets spilled to the stack. It is possible that GCC writes the variable to the stack using a

Bug#871514: clamav: FTBFS on mips64el

2017-08-09 Thread Sebastian Andrzej Siewior
control: reassign -1 gcc-7 7.1.0-12 control: affects -1 clamav On 2017-08-09 16:43:29 [+0200], Aurelien Jarno wrote: > I got a quick look. It's indeed a regression introduced by GCC 7. It can > be workarounded by building the file with -O0, but already appears with > -O1 optimization. > > I got

Bug#871514: clamav: FTBFS on mips64el

2017-08-09 Thread Aurelien Jarno
On 2017-08-08 20:41, Sebastian Andrzej Siewior wrote: > On 2017-08-08 20:34:37 [+0200], To sub...@bugs.debian.org wrote: > … > > returned (the important part): > > |LibClamAV debug: parseEmailBody() rc 1 infect 0 > > |LibClamAV debug: parseEmailBody() returning 3 > … > > The exp build passed with

Bug#871514: clamav: FTBFS on mips64el

2017-08-08 Thread Sebastian Andrzej Siewior
On 2017-08-08 20:34:37 [+0200], To sub...@bugs.debian.org wrote: … > returned (the important part): > |LibClamAV debug: parseEmailBody() rc 1 infect 0 > |LibClamAV debug: parseEmailBody() returning 3 … > The exp build passed with gcc-6_6.4.0-1 [0]. Is there an easy way to > downgrade the compiler

Bug#871514: clamav: FTBFS on mips64el

2017-08-08 Thread Sebastian Andrzej Siewior
Package: clamav Version: 0.99.2+dfsg-6 Severity: serious The last build of clamav (0.99.3~beta1+dfsg-1) failed on mips64el. However the build in experimtal (0.99.3~snapshot…) succeeded and code change is very minimal (almost non-existing). The I tried 0.99.2+dfsg-6 on eller and it failed, too but