summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Smith <psmith@gnu.org>2013-04-14 16:31:18 -0400
committerPaul Smith <psmith@gnu.org>2013-04-14 16:31:18 -0400
commit4bf3c33f83e79951c3860297b6420e64032f04a7 (patch)
tree17a7162ec39c5c58a71d332d53142de6efc246c1 /doc
parentcb64352c75f0da8979c9addd37b2b78bb97d5301 (diff)
downloadgunmake-4bf3c33f83e79951c3860297b6420e64032f04a7.tar.gz
Rename the "parallel-sync" option to "output-sync".
Diffstat (limited to 'doc')
-rw-r--r--doc/make.texi36
1 files changed, 20 insertions, 16 deletions
diff --git a/doc/make.texi b/doc/make.texi
index 1a760e1..e004984 100644
--- a/doc/make.texi
+++ b/doc/make.texi
@@ -4057,12 +4057,13 @@ If there is nothing looking like an integer after the @samp{-j} option,
there is no limit on the number of job slots. The default number of job
slots is one, which means serial execution (one thing at a time).
-One consequence of running several recipes simultaneously is that by
-default, output from each recipe appears as soon as it is generated,
-with the result that messages from different recipes may be interspersed.
-This may create problems in interpreting output. If the @samp{-P} option
-is used, however, recipes will save their output until completion and
-then take turns writing it, with a more coherent result.
+When running several recipes simultaneously the output from each
+recipe appears as soon as it is generated, with the result that
+messages from different recipes may be interspersed. To avoid this
+you can use the @samp{--output-sync} (@samp{-O}) option; if this
+option is provided then the output from each recipe will be saved
+until the recipe is complete, then written all at once. This ensures
+that output from different recipes is not mixed together.
Another problem is that two processes cannot both take input from the
same device; so to make sure that only one recipe tries to take input
@@ -8615,22 +8616,25 @@ The data base output contains file name and line number information for
recipe and variable definitions, so it can be a useful debugging tool
in complex environments.
-@item -P
-@cindex @code{-P}
-@itemx --parallel-sync
-@cindex @code{--parallel-sync}
-@cindex parallel recipe execution, output
-When jobs are running in parallel under @samp{--jobs}, the output of
-each job is held until the job is complete thus ensuring that the output
-of each recipe is grouped together.
+@item -O
+@cindex @code{-O}
+@itemx --output-sync
+@cindex @code{--output-sync}
+@cindex output of parallel execution
+@cindex parallel execution, output of
+Ensure that the complete output from each recipe is printed in one
+uninterrupted sequence. This option is only useful when using the
+@code{--jobs} option to run multiple recipes simultaneously
+(@pxref{Parallel, ,Parallel Execution}). Without this option output
+will be displayed as it is generated by the recipes.
With no argument or the argument @samp{1}, messages from each job in
recursive makes are grouped together. With the argument @samp{2}, the
complete output from any recursive make is grouped together. The latter
achieves better grouping of output from related jobs, but causes longer
delay, since messages do not appear until the recursive make has
-completed. Therefore @samp{-P} is more useful when watching the output
-while make runs, and @samp{-P2} is better suited when running a complex
+completed. Therefore @samp{-O} is more useful when watching the output
+while make runs, and @samp{-O2} is better suited when running a complex
parallel build in the background and checking its output afterwards.
@item -q