On Mon, Dec 24, 2018 at 12:20:05AM +0000, Steve McIntyre wrote: >Package: src:libmcrypt >Version: 2.5.8-3.3 >Severity: serious >Tags: ftbfs >Justification: fails to build from source (but built successfully in the past) > >Hi! > >I've been doing a full rebuild of the Debian archive, building all >source packages targeting armel and armhf using arm64 hardware. We are >planning in future to move all of our 32-bit armel/armhf builds to >using arm64 machines, so this rebuild is to identify packages that >might have problems with this configuration. > >While doing this, I found that libmcrypt failed its test suite for >armel running on arm64: > >... >Algorithm: enigma... failed compatibility >Expected: f3edda7da20f8975884600f014d32c7a08e59d7b >Got: 216540d5d71ec2d57f626a5609a3ebedbb9b32e4 >... > >I've tested on amd64 and things look fine, but building for arm64 on >arm64 also fails with exactly the same test failure as armel-on-arm64.
Just retested again today at a BSP. The failing test (the enigma self-test) works OK on amd64, but fails reliably and repeatedly on at least arm64, armhf and ppc64el with the same failing result. I can only assume that something has changed in compiler setup here - these tests all passed when last uploaded over 4 years ago. Last "maintainer" upload in 2009. Arg. :-( -- Steve McIntyre, Cambridge, UK. st...@einval.com "I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site..." -- Simon Booth
