On Monday 26 January 2009 09:14:21 cpghost wrote:
On Sun, Jan 25, 2009 at 10:41:05PM -0900, Mel wrote:
On Sunday 25 January 2009 20:48:22 Doug Barton wrote:
Josh Carroll wrote:
What I do is the following via make.conf,
I think this is a good solution. Given that incredible
On Sun, Jan 25, 2009 at 10:41:05PM -0900, Mel wrote:
On Sunday 25 January 2009 20:48:22 Doug Barton wrote:
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
snip
That would be absolutely perfect!
+1
snip
Memory may fail me, but wasn't there a GSoC project to parallelize
the ports infrastructure? Or was that about building many different
ports simultaneously instead of one port on multiple cores?
-cpghost.
On Monday 26 January 2009 14:56:10 Eitan Adler wrote:
snip
That would be absolutely perfect!
+1
snip
Memory may fail me, but wasn't there a GSoC project to parallelize
the ports infrastructure? Or was that about building many different
ports simultaneously instead of one port on
before building,
thus using the manual parallel step before.
So, how can portmaster run 'make -jN build' instead of
simple 'make build'?
(I know about portmaster's -m option, but passing -jN to
it won't work, as it would also try to apply this to other
phases than make build).
Thanks,
-cpghost
On Sun, Jan 25, 2009 at 4:44 PM, cpghost cpgh...@cordula.ws wrote:
To build ports in parallel on a 4 core machine, I usually
do this manually:
# cd /usr/ports/some/port
# make configure make -j5 build make install clean
because all steps except make build are not compatible
with -jN
On Sun, Jan 25, 2009 at 05:22:04PM -0500, Josh Carroll wrote:
On Sun, Jan 25, 2009 at 4:44 PM, cpghost cpgh...@cordula.ws wrote:
To build ports in parallel on a 4 core machine, I usually
do this manually:
# cd /usr/ports/some/port
# make configure make -j5 build make install clean
On Sun, 25 Jan 2009 23:46:54 +0100
cpghost cpgh...@cordula.ws wrote:
That's a good hint indeed. I'll try it. Maybe I'll modify it a bit to
include ONLY the build target, because -jN fails on nearly every
other target, AFAICS.
Don't forget that there are two different makes; BSD make does the
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
On Sunday 25 January 2009 20:48:22 Doug Barton wrote:
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
10 matches
Mail list logo
