On Sat, 3 Dec 2011 10:37:51 -0500, Indi wrote: > > that is not the verbose flag, but silent-build. > > Hmm, I always thought the "-v" was the verbose switch, and that it > should work properly regardless of what's in make.conf. It *used* to > work properly here, I've been using "emerge -vauND world" to update for > ages...
-v affects the verbosity of emerge, not of gcc, the output of which is still hidden. Thisis a useful distinction, I prefer to see everything that portage has to tell me without spamming my screen with gcc output. > > If you want the old > > behaviour back, you can add > > > > EMERGE_DEFAULT_OPTS="--quiet-build=n" > > > > to your make.conf > Even including this in make.conf, I still get "quiet-build mode": > > EMERGE_DEFAULT_OPTS="--quiet-build=n" > EMERGE_DEFAULT_OPTS="--verbose" > > The only thing that works is manually using "--quiet-build=n" on the > command line, so it seems the real problem here is "emerge ignoring > EMERGE_DEFAULT_OPTS entries in make.conf". Is it that your second setting overrides the first? Try putting all the settings in one variable assignation. -- Neil Bothwick Top Oxymorons Number 38: Government organization
signature.asc
Description: PGP signature
