Your message dated Tue, 3 Apr 2012 06:39:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#615848: /usr/bin/dpkg-buildpackage: default to
parallel build ( -j<n> ) on multiprocessor machines
has caused the Debian Bug report #615848,
regarding /usr/bin/dpkg-buildpackage: default to parallel build ( -j<n> ) on
multiprocessor machines
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
615848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615848
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.15.8.10
Severity: wishlist
File: /usr/bin/dpkg-buildpackage
When running dpkg-buildpackage on a multiprocessor machine it is usually
desirable to use all the avalable procesors for build but it has to be
selected by an option.
Of course, there are situations when limiting the number of processors
is desirable (eg. to leave some processors for other tasks or to build
broken packages which don't build in parallel) and for this the -j<n>
option can be used.
I am asking here only for a default <n> that makes more sense.
Thanks
Michal
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (900, 'stable'), (700, 'oldstable'), (510, 'unstable'), (200,
'experimental'), (111, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-3-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg-dev depends on:
ii base-files 6.0 Debian base system miscellaneous f
ii binutils 2.20.1-16 The GNU assembler, linker and bina
ii bzip2 1.0.5-6 high-quality block-sorting file co
ii libdpkg-perl 1.15.8.10 Dpkg perl modules
ii make 3.81-8 An utility for Directing compilati
ii patch 2.6-2 Apply a diff file to an original
ii xz-utils 5.0.0-2 XZ-format compression utilities
Versions of packages dpkg-dev recommends:
ii bcc [c-compiler] 0.16.17-3.1 16-bit x86 C compiler
ii build-essential 11.5 Informational list of build-essent
ii fakeroot 1.14.4-1 Gives a fake root environment
ii gcc [c-compiler] 4:4.4.5-1 The GNU C compiler
ii gcc-4.4 [c-compiler] 4.4.5-8 The GNU C compiler
ii gnupg 1.4.10-4 GNU privacy guard - a free PGP rep
ii gpgv 1.4.10-4 GNU privacy guard - signature veri
ii libalgorithm-merge-perl 0.08-2 Perl module for three-way merge of
Versions of packages dpkg-dev suggests:
ii debian-keyring 2010.12.29 GnuPG keys of Debian Developers
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 2011-02-28 at 13:43:26 +0100, Michal Suchanek wrote:
> Package: dpkg-dev
> Version: 1.15.8.10
> Severity: wishlist
> File: /usr/bin/dpkg-buildpackage
> When running dpkg-buildpackage on a multiprocessor machine it is usually
> desirable to use all the avalable procesors for build but it has to be
> selected by an option.
>
> Of course, there are situations when limiting the number of processors
> is desirable (eg. to leave some processors for other tasks or to build
> broken packages which don't build in parallel) and for this the -j<n>
> option can be used.
>
> I am asking here only for a default <n> that makes more sense.
There's never a good default for n > 1, and this is a decision that
should always fall in the hands of the builder. Because no heuristic
will ever get this right, there's no point trying.
Closing this wontfix bug.
thanks,
guillem
--- End Message ---
