tips for understanding systemtap build failure?

[Timo Juhani Lindfors <timo.lindfors@iki.fi>]

Hi,

systemtap 1.7-1~experimental1 seems to FTBFS on s390x and sparc in a
somewhat confusing way:

   dh_link -a
   debian/rules override_dh_compress
make[1]: Entering directory `/build/buildd-systemtap_1.7-1~experimental1-s390x-l1KAR4/systemtap-1.7'
make[1]: warning: -jN forced in submake: disabling jobserver mode.
dh_compress -X.stp -X.wav -Xsocktop -Xsyscalltimes -X.pdf
make[1]: Leaving directory `/build/buildd-systemtap_1.7-1~experimental1-s390x-l1KAR4/systemtap-1.7'
   debian/rules override_dh_fixperms
make[1]: Entering directory `/build/buildd-systemtap_1.7-1~experimental1-s390x-l1KAR4/systemtap-1.7'
make[1]: warning: -jN forced in submake: disabling jobserver mode.
dh_fixperms
chmod 4754 debian/systemtap-runtime/usr/bin/staprun
chmod: cannot access `debian/systemtap-runtime/usr/bin/staprun': No such file or directory
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory `/build/buildd-systemtap_1.7-1~experimental1-s390x-l1KAR4/systemtap-1.7'
make: *** [binary-arch] Error 2

https://buildd.debian.org/status/package.php?p=systemtap&suite=experimental

Porterbox does not seem to have the required build-dependencies
installed in the chroot so I can not reproduce this myself.

Any tips?