I wanted to view logs for an emerge, and specified --quiet-build n on the emerge command line (found via the manpage). This does not print anything to stdout, however, if --jobs is specified (in this case, in make.conf).
adding --jobs=1 worked around it.
Please update the manpage to reflect that (and/or preferably issue a warning if --quiet-build n is specified while --jobs is).
Steps to Reproduce:
emerge --quiet-build n sys-devel/gcc
gcc builds, with quiet output
gcc builds, with output going to stdout
This is explained under --jobs in man emerge:
-j [JOBS], --jobs[=JOBS]
Specifies the number of packages to build simultaneously. If this
option is given without an argument, emerge will not limit the
number of jobs that can run simultaneously. Also see the related
--load-average option. Similarly to the --quiet-build option, the
--jobs option causes all build output to be redirected to logs.
Note that interactive packages currently force a setting of
--jobs=1. This issue can be temporarily avoided by specifying
It doesn't make sense to randomly intersperse multiple jobs' output.
If you want to see the output of the build, tail -f $PORTAGE_TMPDIR/$P/temp/build.log.
Created attachment 373160 [details, diff]
Please consider this patch to the manpage.
(In reply to email@example.com from comment #3)
> Created attachment 373160 [details, diff] [details, diff]
> manpage patch
> Please consider this patch to the manpage.
Looks good to me.
I've posted the patch for review here:
This is in the master branch now:
Released in portage-2.2.16.