Date: Sun, 25 Jan 2009 21:48:22 -0800 From: Doug Barton <dougb@FreeBSD.org> To: josh.carroll@gmail.com Cc: cpghost <cpghost@cordula.ws>, freebsd-questions@freebsd.org Subject: Re: make -jN build with portmaster Message-ID: <497D4EA6.1020100@FreeBSD.org> In-Reply-To: <8cb6106e0901251422q1412ed38gd14f7591d4dfcabd@mail.gmail.com> References: <20090125214457.GA4568@phenom.cordula.ws> <8cb6106e0901251422q1412ed38gd14f7591d4dfcabd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Josh Carroll wrote:
> What I do is the following via make.conf,
I think this is a good solution. Given that incredible foot-shooting
power of the -j stuff I am not inclined to add something like this to
portmaster, not even as an "advanced" option.
Doug
> which will work for
> portmaster/portupgrade or manual builds:
>
> # set MAKE_ARGS for the build target(s)
> .if !(make(*install) || make(package))
> MAKE_ARGS+=-j8
> .endif
>
> Then as you find ports that don't build properly, add an entry like this:
>
> # some ports don't like -j8, so we can undo the MAKE_ARGS addition for those
> .if ${.CURDIR:M*/multimedia/mplayer}
> MAKE_ARGS:=${MAKE_ARGS:C/-j8//}
> .endif
>
> It's a bit of a hack, but I've had decent success with this. Enough
> ports fail to build with -jX, that I'd never do the above on a
> production machine, especially since it's possible for some sort of
> silent error that produces an unpredictable binary. But for my home
> machine, I've been pretty happy with it.
>
> Regards,
> Josh
>
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?497D4EA6.1020100>