No subject

automatically default to the number of available CPUs in any case, so
should automatically be 1 at least on the porter box.

However, assuming that adding the following to debian/rules would
implement your suggestion, then sadly no it does not appear to be enough:

waf-configure-options += $(if $(filter hppa,$(DEB_HOST_ARCH)),-j1)

Even with this change, the "./waf configure" call hangs after outputting

Checking for dbus-1 >= 1.0.0             : ok
Checking for dbus-1 flags                : ok
Checking for header expat.h              : ok

I killed it after 15 minutes of inactivity; the build output shows that
-j1 was passed to the configure call. If I add the Runner.py patch
instead, it gets past that point with ease (and later fails with the
second error I mentioned, which is trivially fixable by adding "&&
!defined(__hppa__)" to an existing patch).

Regards,

Adam