On Mon, May 28, 2018 at 02:07:00PM -0500, Rob Browning wrote: > Hmm, I cannot reproduce that here in a 2.2.3+1-4 git tree via: > > DEB_BUILD_PROFILES="cross nocheck" \ > DEB_BUILD_OPTIONS="parallel=2 nocheck" \ > nice fakeroot dpkg-architecture -amipsel -c dpkg-buildpackage -B > > on an amd64 machine that's somewhere between stretch and buster. I lost > the log (I can retry if it seems advisable), but at the end it didn't > appear to be building anything mipsel-related.
I'm sorry, I don't usually build with dpkg-buildpackage directly and thus I messed up the instructions. dpkg-buildpackage has its own --host-arch switch. Please try: DEB_BUILD_PROFILES="cross nocheck" \ DEB_BUILD_OPTIONS="parallel=2 nocheck" \ nice fakeroot dpkg-buildpackage -B --host-arch=mipsel > Any thoughts about what might be best to try next? Initially, I thought the failure was 100% reproducible for any architecture. That doesn't seem to be the case. Let me try building guile-2.2 for most release architecture with sbuild: arm64: successful armel: ftcbfs, ftcbfs armhf: ftcbfs, ftcbfs mips: multiarch skew linux-libc-dev mips64el: successful mipsel: multiarch skew linux-libc-dev powerpc: ftcbfs, ftcbfs ppc64el: successful s390x: ftcbfs I ran each ftcbfs build twice to rule out the possibility of a random ftcbfs. So we have a non-random ftcbfs for some architectures. I'm a bit surprised about s390x here as it is the only failing 64bit architecture. Hope this helps Helmut
