[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: parallel make and I/O of child processes
From: |
Ralf Wildenhues |
Subject: |
Re: parallel make and I/O of child processes |
Date: |
Tue, 25 Jan 2011 07:47:18 +0100 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
* Stefano Lattarini wrote on Mon, Jan 24, 2011 at 11:38:28PM CET:
> Subject: [PATCH] docs: color-tests issues with parallel make
>
> * doc/automake.texi (Simple Tests): Document that automatic
> recognition of a capable terminal attached to stdout can fail
> with some make implementation when running in parallel mode,
> thus causing colored test output not to be automatically
> activated when it should.
OK for maint with nits addressed.
Thanks,
Ralf
> --- a/doc/automake.texi
> +++ b/doc/automake.texi
> @@ -8589,6 +8589,12 @@ colored output by setting the @command{make} variable
> @samp{AM_COLOR_TESTS=no}, or force colored output even without a connecting
> terminal with @samp{AM_COLOR_TESTS=always}.
>
> +Note that incompatible semantics of some @command{make} implementations
I'm not sure "incompatible" is right here, as there is no standard to
adhere to. It seems s/incompatible/the/ would be more neutral.
> +when used in parallel mode (@pxref{Parallel make,,, autoconf, The Autoconf
> +Manual}) can cause the automatic detection of a connection to a capable
> +terminal to fail spuriously. In that case, you can still resort to the
s/spuriously//
> +use of @samp{AM_COLOR_TESTS=always}.
> +
> @vindex TESTS
> @vindex TESTS_ENVIRONMENT
> The variable @code{TESTS_ENVIRONMENT} can be used to set environment