dpkg-buildpackage parameter -j not given to make
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In building a debian package the command dpkg-buildpackage does not hand parameter "-j6" to the make command. The make command keeps getting called with parameter "-j1".
This contradicts with the description for command dpkg-buildpackage. Warning: next to controlling parameter for command make, this parameter seems to control setting parallel=jobs in the DEB_BUILD_OPTIONS variable (not known to me).
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: dpkg-dev 1.16.10ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Mon Sep 23 23:15:10 2013
InstallationDate: Installed on 2013-05-16 (130 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
PackageArchitec
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dpkg
UpgradeStatus: No upgrade log present (probably fresh install)
Could you take a look at the offending debian/rules? This is probably because it's calling dh without --parallel.
From `man dh`:
If your package can be built in parallel, you can support parallel
building as follows. Then dpkg-buildpackage -j will work.
#!/usr/bin/make -f
%:
dh $@ --parallel
And from `man debhelper`:
--parallel
Enable parallel builds if underlying build system supports them.
The number of parallel jobs is controlled by the DEB_BUILD_OPTIONS
environment variable ("Debian Policy, section 4.9.1") at build
time. It might also be subject to a build system specific limit.
If this option is not specified, debhelper currently defaults to
not allowing parallel package builds.
I *think* the way this works is cdbs will figure out to set the --parallel parameter on its own, but if our rules file doesn't do that, it isn't going to happen. So, I think the core issue here is that the documentation for dpkg-buildpackage is a little misleading, or at least isn't as helpful as it really should be.