Bug 565216 – sys-apps/portage: emerge: NOCOLOR functionality does not work with gcc-4.9

• Status: CONFIRMED
• Product: Portage Development

[Description Agostino Sarubbo 2015-11-09 11:43:54 UTC]

I have NOCOLOR="1" in my make.conf but I'm not able to produce output without colors. Maybe it is a faul of the newer gcc.

Does it work for you?

[Comment 1 Agostino Sarubbo 2015-11-09 11:45:01 UTC]

Created attachment 416356 [details]
linux-gpib-3.2.21-r1:20151109-113628.log

example

[Comment 2 Zac Medico 2015-11-09 14:57:15 UTC]

Is that GCC_COLORS variable set? You can add -fdiagnostics-color=never to CFLAGS.

[Comment 3 Agostino Sarubbo 2015-11-09 15:15:47 UTC]

(In reply to Zac Medico from comment #2)
> Is that GCC_COLORS variable set? You can add -fdiagnostics-color=never to
> CFLAGS.

GCC_COLORS is not set. Should it be?

-fdiagnostics-color=never does not suppress all colors..

[Comment 4 SpanKY 2015-11-09 19:14:26 UTC]

i don't see anything for toolchain@ to do here, so dropping cc.

if portage wants to propagate NOCOLORS=1 into also exporting GCC_COLORS=, that sounds fine.

[Comment 5 Zac Medico 2015-11-09 20:13:50 UTC]

It says here that setting GCC_COLORS to an empty string will disable colors:

https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html

[Comment 6 Zac Medico 2015-11-09 20:15:47 UTC]

You can also try -fno-diagnostics-color in CFLAGS.

[Comment 7 SpanKY 2015-11-09 21:20:28 UTC]

(In reply to Zac Medico from comment #5)

right ... that should be fairly safe for portage to do rather than trying to detect whether the active compiler supports the flag