Right, of course :-) That is the obvious reason for using files, thanks! I was biased against writing things to disc which is probably silly, because it's probably not slow when compared to the size of the job that's running.
Stdout and stderr will now all be stdout, BTW (no matter what method one uses) but that's not generally such a problem. Regards, Tim On 14 April 2011 21:18, Paul Smith <psm...@gnu.org> wrote: > On Thu, 2011-04-14 at 20:59 +0100, Tim Murphy wrote: >> To prevent any kind of deadlock you sort of want to empty everything >> the stderr and stdout pipe buffers may contain. >> >> It is conceivable that the stdout pipe might contain two lines of text >> and stderr pipe might contain 1 by the time your select statement (or >> waitformultipleobjects) has woken up. > > This would all be true, if anyone were using pipes and select > statements... but we're not :-) > > The implementation David provided has all the output going to temporary > files, which are then read and printed to stdout or stderr (and deleted) > when the job gets the output sync lock. > > To choose between merged and not merged you just choose between creating > distinct files, vs. creating one file and setting both stdout/stderr to > write to it... same as it would write to the tty device. > > -- > ------------------------------------------------------------------------------- > Paul D. Smith <psm...@gnu.org> Find some GNU make tips at: > http://www.gnu.org http://make.mad-scientist.net > "Please remain calm...I may be mad, but I am a professional." --Mad Scientist > > -- You could help some brave and decent people to have access to uncensored news by making a donation at: http://www.thezimbabwean.co.uk/ _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
