Bug#1000235: 0ad: Ignore parallel jobs limit during building

Boyuan Yang byang at debian.org
Sat Nov 20 00:48:39 GMT 2021


Source: 0ad
Severity: important
Version: 0.0.25b-1
X-Debbugs-CC: vcheng at debian.org rousseau at debian.org

Dear 0ad package maintainers,

https://sources.debian.org/src/0ad/0.0.25b-1/debian/rules/#L15 :

PARALLEL_JOBS=$(shell getconf _NPROCESSORS_ONLN)
ifeq ($(findstring parallel=,$(DEB_BUILD_OPTIONS)),)
	export DEB_BUILD_OPTIONS+=parallel=$(PARALLEL_JOBS)
endif

This really does not make sense; specifying parallel jobs to be the same as
CPU core number will override -j parameter passed to dpkg-buildpackage and
external DEB_BUILD_OPTIONS environment variable (if defined), which may cause
troubles. For example, when preparing backport build for 0ad, my build machine
OOMed due to having too many CPU cores but limited RAM.

Looking back in git history, the idea of using max CPU core seems to be
introduced in ad2190ed4 back in 2012. I am not sure about the rationale behind
it, but perhaps we should drop it in future uploads.

-- 
Thanks,
Boyuan Yang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-games-devel/attachments/20211119/2490c19d/attachment.sig>


More information about the Pkg-games-devel mailing list