HEADS UP multi processor compilations for everyone

Coleman Kane cokane at FreeBSD.org
Tue Mar 24 09:29:57 PDT 2009


On Tue, 2009-03-24 at 16:19 +0100, Pav Lucistnik wrote:
> Coleman Kane píše v út 24. 03. 2009 v 10:58 -0400:
> > On Tue, 2009-03-24 at 15:54 +0100, Pav Lucistnik wrote:
> > > Niclas Zeising píše v út 24. 03. 2009 v 15:28 +0100:
> > > 
> > > > Not to nitpick or be an annoyance, but you might want to document this 
> > > > in ports(7) or make.conf(5) (or both) so it doesn't get lost in the 
> > > > mail-lists or if people are not reading ports@
> > > 
> > > I will document it soon, thinking The Handbook would be best place.
> > > 
> > 
> > Definitely add it to UPDATING too. This will allow people who typically
> > do something like "make configure && make -j3" to now know that they
> 
> This would break very fast -- it's passing -j3 to port Makefile instead
> of vendor Makefile.

This has worked fine for me for countless years, except where the
vendor's Makefiles were not parallel-safe. This has been my trick to get
larger things (like mysql or xorg-server) to make in parallel. It *did*
work. If this has changed, then it definitely warrants mention in
UPDATING.

> 
> > don't have to. It will also allow others to know why ports compilation
> > on their multi-core boxes suddenly uses a lot more CPU time.
> 
> Same CPU time, less wall time, more CPU utilization :)
> 

Thanks for the clarification... that's what I meant :)

-- 
Coleman Kane
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20090324/f1e7334b/attachment.pgp


More information about the freebsd-ports mailing list