Re: [RFC]serialize the output of parallel make?

[Chiheng Xu]

On Fri, Jul 30, 2010 at 3:45 PM, Philip Guenther <address@hidden> wrote:
> On Thu, Jul 29, 2010 at 11:29 PM, Chiheng Xu <address@hidden> wrote:
> ...
>> My suggestion is that you can implement it as an optional command line
>> option(like -j), and on one or two primary platforms(Linux/Windows),
>> instead of on all platforms.
>
> So, the complexity of both possibilities.  You're writing, debugging,
> and contributing this code yourself?
>

Nop, I'm not maintainer of make,  just a user :)  .


> (I would hope that this wouldn't require any Linux-specific code;
> perhaps you meant "POSIX & Windows"?)
>

Yes.

>
> ...
>> The scenario like "make -j4 2>/dev/null" may be very rare, but
>> scenario like "make -j4  2>&1 |  tee output.txt" may be common.
>
> And what, exactly, are you suggesting that make do to reflect that
> guess about usage patterns?
>
>
> Philip Guenther
>

I mean, normal user of make does not differentiate stdout or stderr
very seriously, they see them both as "output". They want serialized
"output",  whether or not it's stdout or stderr.



-- 
Chiheng Xu
Wuhan,China