Date: Wed, 25 Mar 2009 12:51:52 +0300 From: Anonymous <swell.k@gmail.com> To: pav@FreeBSD.org Cc: ports@FreeBSD.org Subject: Re: HEADS UP multi processor compilations for everyone Message-ID: <86eiwmvsjr.fsf@gmail.com> In-Reply-To: <1237970433.41376.4.camel@pav.hide.vol.cz> (Pav Lucistnik's message of "Wed, 25 Mar 2009 09:40:33 %2B0100") References: <1237901632.1849.19.camel@pav.hide.vol.cz> <86eiwmglso.fsf@gmail.com> <1237970433.41376.4.camel@pav.hide.vol.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Pav Lucistnik <pav@FreeBSD.org> writes: > Anonymous píše v st 25. 03. 2009 v 09:26 +0300: >> Pav Lucistnik <pav@FreeBSD.org> writes: >> >> > If you are FreeBSD port maintainer: >> >> I'm not one. >> >> > >> > Nothing changes for you, if you don't want. If you want to enable the >> > use of multiple cores in your port, add MAKE_JOBS_SAFE=yes to a block >> > somewhere below dependency declarations. If you know your port does not >> > handle -jX well, and want to disable it from using -jX even when user >> > forces this feature, use MAKE_JOBS_UNSAFE=yes. And that's all to it. >> >> Not all ports build using make/gmake. Wouldn't it be better to export >> the number of parallel processes so maintainer can decide whether to use >> it in his port build system? For example >> >> Is this completely discouraged? > > I suppose you can use internal variable _MAKE_JOBS directly. Why are you > stripping -j just to add it back again? Oh, so you're not against the idea. The substitution was to be able to easy replace it with something else. FYI, that example went to ports/133054.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86eiwmvsjr.fsf>