Date: Fri, 22 Nov 2013 13:39:27 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Tijl Coosemans <tijl@FreeBSD.org> Cc: Mathieu Arnold <mat@FreeBSD.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Ganael LAPLANCHE <martymac@FreeBSD.org>, ports-committers@freebsd.org Subject: Re: svn commit: r334573 - head/devel/raknet Message-ID: <20131122133927.GA28902@FreeBSD.org> In-Reply-To: <20131122142038.7e4f35a0@kalimero.tijl.coosemans.org> References: <201311221131.rAMBVEeU056491@svn.freebsd.org> <4A32B27D1E6D98F73F717130@atuin.in.mat.cc> <20131122125248.22d4bdfd@kalimero.tijl.coosemans.org> <E51BE94E2AF75E549E4120C6@atuin.in.mat.cc> <20131122142038.7e4f35a0@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 22, 2013 at 02:20:38PM +0100, Tijl Coosemans wrote: > On Fri, 22 Nov 2013 13:02:03 +0100 Mathieu Arnold wrote: > > Ah, I did not know that. Is it by design ? Do any other make do that ? I'll > > have to check perl@ ports I have removed quite a lot of parenthesis. > > It's by design and I'm not aware of any other make implementation doing > that. It's mentioned in the FreeBSD 10 manpage for make (SHELL COMMANDS > section). > > For ports I don't think this matters much. The -j flag is only used > during build so only if a port is built with FreeBSD make you might > have to patch makefiles to make them jobs-safe. Not to mention that currently our ports framework is inherently -jX unsafe on a much larger scale. I know that some folks are thinking of ways to address this problem in the future (probably distant one though). ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131122133927.GA28902>