[Buildroot] [PATCH RFC] core: enable per-package log files

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Oct 18 07:58:26 UTC 2017


Hello,

On Wed, 18 Oct 2017 09:44:36 +0200, Anisse Astier wrote:

> > I'm not sure how to handle the MESSAGE macro. One suggestion you made
> > was to output directly to the tty. But a big drawback of that is that
> > if you redirect the build output (make 2>&1 | tee logfile) then the
> > messages displayed by the MESSAGE macro will no longer be stored in the
> > logfile, which is super annoying: I always use them to navigate in the
> > logfile to the appropriate place. So I believe directly writing to the
> > tty in the MESSAGE macro is not a good option.  
> 
> I think Arnout meant that the MESSAGE macro could write to both the tty
> (if available) and stdout, hence getting the best of both worlds.

Well, in this case, you'd get the message twice on your terminal if you
run "make 2>&1 | tee logfile". Only one of the two will be saved in the
log file, but both of them will be visible on your tty.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com


More information about the buildroot mailing list