On Wed, 07 Dec 2011 12:26:12 +0200, Nikos Chantziaras wrote: > > Not only did I mean to finish it, I thought I had. Using --jobs>1 sets > > the quiet-build flag > > It also sets it if you don't use more than 1 job. As another poster > (Hinnerk) already mentioned, the only way to get the old behavior back > is to use the "--quiet-build=n" option.
What I said in the text that disappeared from the original post was that --jobs has always hidden the gcc output, long before the quiet-build option appeared. The new option only makes emerge behave the same when -jobs is not set or set to 1. -- Neil Bothwick Ask a silly person, get a silly answer
signature.asc
Description: PGP signature
