Source: libmemcached Version: 1.0.17-2 Severity: minor Tags: patch Hi,
it seems libmemcached has its own way to do a parallel building, i.e. it detects (only on Mac OS X and Linux, otherwise failling back to 1) the number of CPUs, and then it appends -jN+1 to the build flags. This, however, gives few of issues: - sometimes the machine/hardware/whatever could not stand more build jobs than the CPU count - it is unconditional, and you have no way to disable it in a Debian build - it is not possible to actually tune the number of wanted jobs (e.g. you could use just some of the available CPUs, because of others used for something else) - conflicts with debhelper's parallel building facilities Luckly, there is a configure option to disable such behaviour. The attached patch fixes the parallel build in Debian builds: - disable the libmemcached-provided -jN addition - make use of debhelper's parallel facilities (which can be configured adding parallel=N in DEB_BUILD_OPTIONS, see also Policy ยง4.9.1) Thanks, -- Pino
--- a/debian/rules +++ b/debian/rules @@ -3,7 +3,10 @@ TMP=$(CURDIR)/debian/tmp/ %: - dh $@ --with autoreconf + dh $@ --parallel --with autoreconf + +override_dh_auto_configure: + dh_auto_configure -- --enable-jobserver=no override_dh_auto_install: dh_auto_install
