Gentoo Archives: gentoo-user

From: Hinnerk van Bruinehsen <h.v.bruinehsen@×××××××××.de>
To: gentoo-user@l.g.o
Subject: Re: Emerge ignoring make.conf entries [was Re: [gentoo-user] emerge ignoring -v switch]
Date: Sat, 03 Dec 2011 16:32:41
Message-Id: 4EDA4EDC.7070904@fu-berlin.de
In Reply to: Re: Emerge ignoring make.conf entries [was Re: [gentoo-user] emerge ignoring -v switch] by Neil Bothwick
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 03.12.2011 17:09, Neil Bothwick wrote:
5 > On Sat, 3 Dec 2011 10:37:51 -0500, Indi wrote:
6 >
7 >>> that is not the verbose flag, but silent-build.
8 >>
9 >> Hmm, I always thought the "-v" was the verbose switch, and that
10 >> it should work properly regardless of what's in make.conf. It
11 >> *used* to work properly here, I've been using "emerge -vauND
12 >> world" to update for ages...
13 >
14 > -v affects the verbosity of emerge, not of gcc, the output of which
15 > is still hidden. Thisis a useful distinction, I prefer to see
16 > everything that portage has to tell me without spamming my screen
17 > with gcc output.
18 >
19 >>> If you want the old behaviour back, you can add
20 >>>
21 >>> EMERGE_DEFAULT_OPTS="--quiet-build=n"
22 >>>
23 >>> to your make.conf
24 >
25 >> Even including this in make.conf, I still get "quiet-build
26 >> mode":
27 >>
28 >> EMERGE_DEFAULT_OPTS="--quiet-build=n"
29 >> EMERGE_DEFAULT_OPTS="--verbose"
30 >>
31 >> The only thing that works is manually using "--quiet-build=n" on
32 >> the command line, so it seems the real problem here is "emerge
33 >> ignoring EMERGE_DEFAULT_OPTS entries in make.conf".
34 >
35 > Is it that your second setting overrides the first? Try putting all
36 > the settings in one variable assignation.
37 >
38 >
39 EMERGE_DEFAULT_OPTS="--quiet-build=n --keep-going"
40
41 works for me. I think if you want one option per line something like:
42
43 EMERGE_DEFAULT_OPTS="--quiet-build=n"
44 EMERGE_DEFAULT_OPTS="$EMERGE_DEFAULT_OPTS --verbose"
45
46 would be appropriate. Otherwise you override the first assignment with
47 the second as Neil already stated.
48
49
50
51 -----BEGIN PGP SIGNATURE-----
52 Version: GnuPG v2.0.18 (GNU/Linux)
53 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
54
55 iQEcBAEBAgAGBQJO2k7bAAoJEJwwOFaNFkYcAYYIALsdrs+Ui9IxP5OU66oYEthK
56 4uK9vMsn523Dtvaze05ypiZgMxd+TJekMW27pP2U7BRYrE3pzOmDr6id35I3yMUM
57 i5q18Id13MH/t2c880X9ek2TpWL/+mGTqkWcTM7n/9GuTmguO1kdzqmlyLZ5s4l5
58 etic2ObLv4l4Kwmh50YMn1NEeu2GrG8UDCJFAkIX4debWuOiWH17ShQ4aP722vsA
59 frP6Bhsv+IfbI8Y00JrBP4S5HYmXfMb4lwjINEeBJohfWoKmvE1SzR4CdC7NEPQS
60 Kc1hiBuM9rJMzFUBypuwhJ+iTFBMKoKzhXC6TaCGnaMbqfC4P6JwOzNNjrpQPXM=
61 =AWIf
62 -----END PGP SIGNATURE-----