speed up port compiling using RAM (tmpfs) ???
Kris Kennaway
kris at obsecurity.org
Fri Jan 20 14:26:31 PST 2006
On Fri, Jan 20, 2006 at 04:54:33PM -0500, Sergey Babkin wrote:
> Kris Kennaway wrote:
> >
> > On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote:
> > > >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= <des at des.no>
> > >
> > > >Gary Thorpe <gthorpe at myrealbox.com> writes:
> > > >> This effectively means that you cannot take advantage of SMP to
> > > >> compile FreeBSD's ports collection. That sounds like a big
> > > >> limitation...especially for people trying to speed up bulk builds.
> > > >
> > > >We cannot be held responsible for race conditions in the Makefiles of
> > > >third-party software.
> > >
> > > Well, maybe we can then build multiple ports in parallel.
> > > I guess the way to do it would be to run the top-level make with
> > > -j but then disable it when calling the makefiles of the
> > > individual ports. Not that I have any idea how to actually
> > > do that.
> >
> > It's harder than that, because you need to impose dependency
> > information and mutual exclusion between different makes. e.g. they
> > can't both be compiling the same port at the same time, which will
> > happen if you just do the naive thing.
>
> That's the part that "make -j" is supposed to take care of,
> since it should build in parallel only the targets independent
> of each other.
If (as I said) you impose the correct dependency information.
Currently there is no such information provided.
kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20060120/e281f1de/attachment.bin
More information about the freebsd-hackers
mailing list