build output/logging buffering?

[Erik Joelsson]

This problem was new to me. It seems strange that stderr and stdout 
would behave differently. Both are piped through a separate instance of 
'tee' to preserver the separation on the console, but to get both into 
the logfile.

/Erik

On 2012-06-28 20:16, David Holmes wrote:
> I see that a build will create a build.log by default. I also see I 
> can set VERBOSE= to get back to the older more verbose style of output 
> (eg full compilation commands etc).
>
> But it seems that due to the logging there is some buffering taking 
> place that prevents me from seeing the most recent build output while 
> it is running. I just had a problem where due to a mistyped variable I 
> did a "cd " and then starting trawling my entire home directory, but I 
> couldn't see this in the build output, ie no "cd " was visible, 
> presumably because the output was being buffered.
>
> What I did see, which gave me the hint were a bunch of warnings that 
> presumably went to stderr, not stdout and do did not get buffered.
>
> David