[Buildroot] [PATCH v7 0/8] Top-level parallel build support

Vadim Kochan vadim4j at gmail.com
Mon Feb 25 08:33:10 UTC 2019


Hi Thomas,

On Mon, Feb 25, 2019 at 09:05:43AM +0100, Thomas Petazzoni wrote:
> Hello Vadim,
> 
> On Mon, 25 Feb 2019 03:10:03 +0200
> Vadim Kochan <vadim4j at gmail.com> wrote:
> 
> > I think that in case of per-packages parallel build the logs became
> > messy and meaningless so I send a patch which allows to do per-package
> > logging too:
> > 
> > 	https://patchwork.ozlabs.org/patch/1047549/
> > 
> > this is a POC so it just shows the idea.
> 
> Thanks for proposing this!
> 
> The problem of logging was discussed quite a lot back when I started to
> work on per-package directories. I think we investigated overriding the
> SHELL variable, but couldn't find an approach that worked properly, but
> maybe the approach was different than yours, I need to get back to the
> original discussion.
> 
> Back then, what we concluded is that people could use the "make
> --output-sync=target" option, or "make -Otarget" in short. This option
> buffers the output of make on a per-target basis, and displays this
> output at once when the target has completed. The advantage is that the
> output is no longer garbled, but the drawback is that you don't see
> "live" what is happening: if a package takes 20 minutes to build,
> during 20 minutes you see nothing, and at the end of the 20 minutes,
> you get in one go the full build output of that package.
> 

I changed a bit an approach to log output per-package and per-step, so it
solves the issue of refreshing log for particular step by simply
removing the log file at the beginning of step. Actually these steps logs
might be merged into one at the end of make.

Regards,
Vadim Kochan


More information about the buildroot mailing list