On 08/04/16 20:55, Graham Inggs wrote:
Secondly, it should be possible to reproduce the fault by building in
an armhf schroot on abel.d.o, which has the same hardware as the
buildds. A temporary solution would be to upload armhf binaries built
on asachi.d.o.
It would be useful if someone can reproduce the issue and get a
dissasembly of the failure location.
My gut feeling is that llvm is trying to use neon without first checking
it is supported. Afaict the marvell boards we are using for armhf
buildds (and for the abel.d.o porterbox) don't have neon.
[1]
https://buildd.debian.org/status/package.php?p=llvm-toolchain-3.8&suite=unstable
