Bug#871514: clamav: FTBFS on mips64el

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 passed in the past.

I looked slightly more closely on eller. After a complete build, the
command
|clamscan/clamscan --gen-json --quiet -dunit_tests/test-1/test-db \
|	unit_tests/input/phish-test-clean unit_tests/input/phish-test-cloak \
|	unit_tests/input/phish-test-ssl  --log=clamscan2.log --debug

returned (the important part):
|LibClamAV debug: parseEmailBody() rc 1 infect 0
|LibClamAV debug: parseEmailBody() returning 3

the matching C code by the end of parseEmailBody():
|         cli_dbgmsg("parseEmailBody() rc %d infect %d\n", (int)rc, infected);
|         if ((rc != FAIL) && infected)
|                 rc = VIRUS;
| 
|         cli_dbgmsg("parseEmailBody() returning %d\n", (int)rc);
 
and rc is type mbox_status:
| typedef enum {
|         FAIL,
|         OK,
|         OK_ATTACHMENTS_NOT_SAVED,
|         VIRUS,
|         MAXREC,
|         MAXFILES
| } mbox_status;

So rc is != FAIL and infected is 0 but the compiler manages to set rc to
VIRUS / 3.

The exp build passed with gcc-6_6.4.0-1 [0]. Is there an easy way to
downgrade the compiler on eller/porterbox? Or could a porter double
check this please?

[0] https://buildd.debian.org/status/fetch.php?pkg=clamav&arch=mips64el&ver=0.99.3~snapshot20170704%2Bdfsg-1&stamp=1499981584&raw=0

Sebastian