speed up port compiling using RAM (tmpfs) ???

Sergey Babkin babkin at verizon.net
Fri Jan 20 17:36:22 PST 2006


Kris Kennaway wrote:
> 
> 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.

Ah, so we don't have any reliable information about dependencies 
between the ports either (not just between files inside each 
particular port)?  Hm, I think it would present a problem even 
when building them sequentially.

-SB


More information about the freebsd-hackers mailing list