On Thu, Oct 24, 2013 at 08:24:28PM +0200, Alessandro Ghedini wrote: > Hi all, > > long story short, a couple years ago armel builds for valgrind were enabled > (despite the fact that valgrind only supports ARMv7) by building the package > in > cross-compile mode and forcing the -march=armv7-a option on buildds that > didn't > support ARMv7 natively. This was done so that ARMv7 armel systems could use > valgrind (see #592614). > > This has sort of worked for a while, until a couple months ago when valgrind > started FTBFS on armel (#720409). This was a simple routine rebuild for the > openmpi transition, so I'm inclined to think that I did not broke anything > myself. My next upload 1:3.8.1-5 (a month later) still failed to build, making > me think that this is not a transient failure.
To add a little more context: * 1:3.8.1-4 built on ancina on 2013-06-01 * 1:3.8.1-4+b1 failed twice on ancina on 2013-08-21/22 * 1:3.8.1-5 failed on antheil on 2013-09-24 The fact that it built fine and then 2 months later failed on ancina looks weird to me, and I can't think of any change that could have triggered this. Also, please CC me since I'm not subscibed to the list. Cheers -- perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature