Hello Steve, Since you are doing a study building armhf on arm64 hardware, see below yet another failure example.
Regards Missatge de Daniel Kahn Gillmor <d...@fifthhorseman.net> del dia dj., 22 de nov. 2018 a les 13:49: > > Hi armhf build maintainers-- > > knot-resolver 3.1.0-1 is failing on arm-arm-01: > > > https://buildd.debian.org/status/fetch.php?pkg=knot-resolver&arch=armhf&ver=3.1.0-1&stamp=1542753152&raw=0 > > interestingly, 3.0.0-9 (the previous version) also failed on arm-arm-01: > > > https://buildd.debian.org/status/fetch.php?pkg=knot-resolver&arch=armhf&ver=3.0.0-9&stamp=1536774160&raw=0 > > but it succeeded when given back to hasse: > > > https://buildd.debian.org/status/fetch.php?pkg=knot-resolver&arch=armhf&ver=3.0.0-9&stamp=1541396378&raw=0 > > Both failures on arm-arm-01 appear to have either SIGBUS or "Bus Error" > in them. > > Is there any sort of significant architectural difference between > arm-arm-01 and hasse that i should relay to the upstream developers of > knot-resolver? > > in the meantime, can we do a giveback on armhf to a machine other than > arm-arm-01 to make sure that the latest knot-resolver does actually > build? > > thanks for your work on keeping armhf in good shape in debian, > > --dkg -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.