On Fri, 2015-06-19 at 02:13 +0200, Jaromír Mikeš wrote: > 2015-06-18 22:55 GMT+02:00 James Cowgill <james...@cowgill.org.uk>: > > It's not a concurrent compile issue - the failed build was non > > -parallel. > > > > I've run the build on a few of mipsel machines and it built fine every > > time so I don't think it's a bug in gcc. > > > > Also mips64el built it fine (uses almost the same gcc backend as > > mipsel). Build log: > > http://mipsdebian.imgtec.com/debian/logs/x/x42-plugins/x42-plugins_20150530-1_mips64el-20150601-0647.gz > > > > debian-3a-1 (machine for the mips64el build) is also a loongson machine > > like mipsel-aql-01 so it probably isn't a hardware issue. > > > > The assembler errors sound like whatever data was fed into the > > assembler actually was garbage. I can't really think of anything other > > than it just being a random buildd glitch :/ > > So you are suggesting just simply upload again with all archs allowed?
I think so. You could wait for the ftpmasters to remove the mipsel build and for it to migrate to testing if you want. James
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
