Subject: Re: distcc and make -jN
To: Bruce J.A. Nourish <firstname.lastname@example.org>
From: Juan RP <email@example.com>
Date: 05/19/2004 08:52:40
Content-Type: text/plain; charset=US-ASCII
On Wed, 19 May 2004 05:48:09 +0000
"Bruce J.A. Nourish" <firstname.lastname@example.org> wrote:
> This is almost exactly what I'm doing (I have localhost at the front).
> The problem is, that unless -jN (for N > 1) is specified, this
> configuration is worthless - you would be better not using distcc at
> This is because distcc round-robins through the host list from the
> start each time, passing over a host only if it has exceeded its
> job limit. As -j1 (or no -j option) will only ever cause one job to
> be running at once, only the first host will ever be used.
> Ergo, unless -jN (N > 1) is given, *the use of distcc is a complete
> waste of time* (except in a few very special cases).
> I'm rather inclined to submit a PR on the matter, as it shouldn't
> be that difficult to a create a variable (say, PKG_MAKEFLAGS) to
> pass flags to the make invocation in the package's build stage.
> What does everyone think?
You are right... in that case MAKE_FLAGS is what we need, because it's only
defined in the "do-build" target.
Juan RP <email@example.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)
-----END PGP SIGNATURE-----