From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Setting number of parallel builds for other build-systems than 'make'
Date: Sun, 1 Oct 2006 12:27:13 -0700 [thread overview]
Message-ID: <20061001192713.GA7046@seldon> (raw)
In-Reply-To: <451FF23E.3050301@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]
On Sun, Oct 01, 2006 at 09:52:14AM -0700, Donnie Berkholz wrote:
> Tiziano Müller wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Hi everyone
> >
> >It seems that setting the number of parallel builds using '-jN' does not
> >only work for make, but also for scons and bjam (and maybe others as well).
> >Since it isn't save to assume that '-jN' is the only option in MAKEOPTS,
> >some filtering is needed.
> >Now, SCONSOPTS (BJAMOPTS respectively) could be added to make.conf and used
> >whenever one of those build-systems is being used. But we would probably
> >have to add a ...OPTS for every build-system.
> >
> >What do you think? Better ideas?
>
> I think adding it for each build system is probably a good idea,
> nobody's guaranteeing option-level compatibility with make. Optionally
> falling back to using the few valid MAKEOPTS might be a nice addition.
I might be daft (likely), but why not just introduce a var indicating
max parallelization instead? Tweak portage to push that setting into
MAKEOPTS="${MAKEOPTS+${MAKEOPTS} } -j${PARALLELIZATION}".
Might sound daft, but -j is hardcoded parallelization; if you're
trying to run 3 build processes, the original var of -j isn't all that
useful, nor will the hardcoded -j# var set for 3 package build
processes be useful if you're doing a single build.
Depending on number of seperate package build processes possible, the
# of build processes allocated per build process needs to vary
(essentially).
Now... that's a bit ahead of what portage is doing atm, but folks
*will* parallelize portage building (see bug 147516 if in doubt), so
its not too far out.
Getting back to the actual topic, set this var, it's a raw int that a
scons/bjam eclass can use to easily set appropriate var with the
parallelization requested, thus unifying this particular knob; more
importantly, it gives them a way to do what they're after while
exposing a knob that the pkg manager can easily fiddle with for global
parallelization needs.
Only downside to it I see is that it requires mangling the pkg manager
to translate the parallelization setting into MAKEOPTS+=-j#; can't
really get around that however due to the fact MAKEOPTS is already
forced in installed configuration though.
Thoughts?
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-01 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 13:04 [gentoo-dev] Setting number of parallel builds for other build-systems than 'make' Tiziano Müller
2006-10-01 13:26 ` Diego 'Flameeyes' Pettenò
[not found] ` <45213121.6060605@gentoo.org>
2006-10-02 17:38 ` Diego 'Flameeyes' Pettenò
2006-10-01 16:52 ` Donnie Berkholz
2006-10-01 19:27 ` Brian Harring [this message]
2006-10-17 1:06 ` Mike Frysinger
[not found] ` <20061001142733.0a8b4eac@snowdrop.home>
2006-10-01 17:23 ` [gentoo-dev] " Tiziano Müller
2006-10-01 18:01 ` Ciaran McCreesh
2006-10-01 18:07 ` [gentoo-dev] " Tiziano Müller
2006-10-04 23:31 ` [gentoo-dev] " Ilya A. Volynets-Evenbakh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061001192713.GA7046@seldon \
--to=ferringb@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox