> Package name : re2c Alas, the new version failed to build on five architectures. Even worse, the build logs contain no meaningful output:
.--==== make check-TESTS make[2]: Entering directory '/«PKGBUILDDIR»' make[3]: Entering directory '/«PKGBUILDDIR»' FAIL: run_tests.sh PASS: testrange PASS: testston32unsafe ============================================================================ Testsuite summary for re2c 0.15.3 ============================================================================ # TOTAL: 3 # PASS: 2 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See ./test-suite.log Please report to [email protected] ============================================================================ Makefile:1313: recipe for target 'test-suite.log' failed `--==== Could you please create an "override_dh_auto_test" target in debian/rules that runs "$(MAKE) check" and if it fails, cats test-suite.log? Debugging the failure requires access to a machine, real or emulated, of one of architectures that fail. I suspect that you have no mips, powerpc, s390x, hppa or sparc64 machines lying around -- and access to Debian's porterboxes is restricted to DDs only which makes using them greatly unconvenient. Thus, I'd strongly recommend using qemu. You can either install a virtual machine by hand (which requires reading arch-specific docs) or fetch a pre-made image from https://people.debian.org/~aurel32/qemu/ -- unfortunately, these haven't been updated since wheezy which requires dist-upgrades to jessie then unstable. -- A tit a day keeps the vet away.
