[Buildroot] autoconf caching

[Fabio Porcedda <fabio.porcedda@gmail.com>]

On Fri, Jun 6, 2014 at 6:45 PM, Dallas Clement
<dallas.a.clement@gmail.com> wrote:
> On Fri, Jun 6, 2014 at 11:31 AM, Mike Zick <minimod@morethan.org> wrote:
>>
>> On Fri, 6 Jun 2014 11:14:15 -0500
>> Dallas Clement <dallas.a.clement@gmail.com> wrote:
>>
>> > > Seems a fairly decent setup. You have enough RAM, and a good storage
>> > > system (ideally based on SSDs) ?
>> >
>> > Yep, very speedy SSDs and 64 GB for RAM.  Because of all the
>> > serialization in this build process,
>> > building from a large ram disk seems to make little difference.
>> >
>>
>> Having 7 of your 8 cores sitting in their idle loop is probably your
>> #1 thing to address. . . .
>>
>> With a very large selection of packages, perhaps you could split them
>> into several (8, 9?) Buildroot trees.
>> Then run those buildroot instances as jobs at the same time.
>>
>> Or...
>>
>> At least pull the really big time consumers out, into their own BR
>> instance, and use your idle cores on those.
>>
>> Mike
>>
>
>> Having 7 of your 8 cores sitting in their idle loop is probably your
>> #1 thing to address. . . .
>
> Yes, makes me sick to have them just sitting there...
>
>> With a very large selection of packages, perhaps you could split them
>> into several (8, 9?) Buildroot trees.
>
> This is a good idea.  I think I've exhausted most of the other options
> except for
> commenting out .NOTPARALLEL in the top-level make.  If that doesn't help,
> I will definitely try breaking things up.  Thanks for the tip.

Please let me know if you have any issue using top-level parallel make.
I'm curently testing it and ironing it out.

Best regards
-- 
Fabio Porcedda