1 |
On Sat, May 13, 2017 at 9:25 AM, Miroslav Rovis |
2 |
<miro.rovis@××××××××××××××.hr> wrote: |
3 |
> On 170510-20:03-0400, Walter Dnes wrote: |
4 |
>> On Wed, May 10, 2017 at 01:35:24PM -0500, R0b0t1 wrote |
5 |
>> |
6 |
>> > The option is "-fdiagnostics-color=never" or "-fno-diagnostics-color". |
7 |
>> > You can also set the environment variable GCC_COLORS to the empty |
8 |
>> > string. The latter is probably more useful in the context of portage. |
9 |
>> |
10 |
>> Thank you. I successfully tried... |
11 |
>> |
12 |
>> GCC_COLORS="" emerge icewm |
13 |
> Another tip to remember. |
14 |
> |
15 |
>> I suppose the next step is to add GCC_COLORS="" to make.conf. |
16 |
>> |
17 |
> I wonder why sticking " --color=n" in the EMERGE_DEFAULT_OPTS in |
18 |
> make.conf (e.g. mine is: |
19 |
> |
20 |
> EMERGE_DEFAULT_OPTS="--keep-going --with-bdeps=y --autounmask-keep-masks --ask --verbose --color=n" |
21 |
> |
22 |
> does only partly its job. Erratically, I'd say. You never know if it |
23 |
> will or not remove color... A bug should be posted for that, but I have |
24 |
> a partly broken system at this time... |
25 |
> |
26 |
|
27 |
That switch only handles the coloring of portage output. I suggested |
28 |
using GCC_COLORS precisely because "--color=n" doesn't seem to |
29 |
propagate to subcommands which do output coloring. |
30 |
|
31 |
Another program you might want to disable output coloring for is |
32 |
CMake, using CMAKE_COLOR_MAKEFILE=OFF. |