Control: severity -1 wishlist Hi!
On Fri, 2015-03-20 at 17:22:46 +0000, Edmund Grimley Evans wrote: > Package: dpkg-dev > Version: 1.17.24 > The problem is that when I tried to build a random sample of packages > with sbuild -j4 there were quite a lot of failures. Yes, that's to be expected, not all packages support parallel builds. > I only looked at a couple in detail. For example: > > apt-get source freecdb > cd freecdb-0.75/ > > dpkg-buildpackage -j4 > # fails with something like: directory debian/freecdb missing > > DEB_BUILD_OPTIONS=parallel=4 dpkg-buildpackage > # is fine > > The same happens with "sgmltools-lite", and perhaps a lot of other > packages. > > It seems that "-j4" causes the top-level makefile debian/rules to be > built in parallel, which is unlikely to be useful, and sometimes > doesn't work at all, while DEB_BUILD_OPTIONS=parallel=4 only takes > effect at lower levels. «dpkg-buildpackage -jN» forces the build to be parallel by setting -jN in MAKEFLAGS (which might not affect the package build system if that does not use make). When using DEB_BUILD_OPTIONS=parallel=N the package needs to honor the setting explicitly, and many packages do not honor it, so that value will have not effect. > Could dpkg-buildpackage be modified so that -jN does exactly the same > as DEB_BUILD_OPTIONS=parallel=N? Or could there be a warning in > dpkg-buildpackages's man page that people probably shouldn't use -jN? > Or should we just file bugs against every package that doesn't build > with dpkg-buildpackage -jN? Changing -jN to do the same as DEB_BUILD_OPTIONS=parallel=N would defeat the point of it, which is to be able to easily force parallel builds no matter what. In an ideal world all packages would support parallel builds so using it would just work. I'll document this in the man page for the unwary. :) Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
