Re: [gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[R0b0t1]

On Sat, May 13, 2017 at 7:50 PM, Miroslav Rovis
 wrote:
> On 170513-12:53-0500, R0b0t1 wrote:
>> On Sat, May 13, 2017 at 9:25 AM, Miroslav Rovis
>>  wrote:
>> > On 170510-20:03-0400, Walter Dnes wrote:
>> >> On Wed, May 10, 2017 at 01:35:24PM -0500, R0b0t1 wrote
>> >>
>> >> > The option is "-fdiagnostics-color=never" or "-fno-diagnostics-color".
>> >> > You can also set the environment variable GCC_COLORS to the empty
>> >> > string. The latter is probably more useful in the context of portage.
>> >>
>> >>   Thank you.  I successfully tried...
>> >>
>> >> GCC_COLORS="" emerge icewm
>> > Another tip to remember.
>> >
>> >>   I suppose the next step is to add GCC_COLORS="" to make.conf.
>> >>
>> > I wonder why sticking " --color=n" in the EMERGE_DEFAULT_OPTS in
>> > make.conf (e.g. mine is:
>> >
>> > EMERGE_DEFAULT_OPTS="--keep-going --with-bdeps=y --autounmask-keep-masks 
>> > --ask --verbose --color=n"
>> >
>> > does only partly its job. Erratically, I'd say. You never know if it
>> > will or not remove color... A bug should be posted for that, but I have
>> > a partly broken system at this time...
>> >
>>
>> That switch only handles the coloring of portage output. I suggested
>> using GCC_COLORS precisely because "--color=n" doesn't seem to
>> propagate to subcommands which do output coloring.
>>
>> Another program you might want to disable output coloring for is
>> CMake, using CMAKE_COLOR_MAKEFILE=OFF.
>>
>
> Thanks for the tip! But let me see... Like the above (repasting):
>> >> GCC_COLORS="" emerge icewm
> pr maybe stick in the /etc/portage/bashrc or in some other way?
>

As Walter suggested make.conf seems the ideal place. Should that fail
I'm not entirely sure, as I believe portage does some pretty heavy
environment sandboxing.

Re: [gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[Miroslav Rovis]

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

Thanks for the tip! But let me see... Like the above (repasting):
> >> GCC_COLORS="" emerge icewm
pr maybe stick in the /etc/portage/bashrc or in some other way?

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

Re: [gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[R0b0t1]

On Sat, May 13, 2017 at 9:25 AM, Miroslav Rovis
 wrote:
> On 170510-20:03-0400, Walter Dnes wrote:
>> On Wed, May 10, 2017 at 01:35:24PM -0500, R0b0t1 wrote
>>
>> > The option is "-fdiagnostics-color=never" or "-fno-diagnostics-color".
>> > You can also set the environment variable GCC_COLORS to the empty
>> > string. The latter is probably more useful in the context of portage.
>>
>>   Thank you.  I successfully tried...
>>
>> GCC_COLORS="" emerge icewm
> Another tip to remember.
>
>>   I suppose the next step is to add GCC_COLORS="" to make.conf.
>>
> I wonder why sticking " --color=n" in the EMERGE_DEFAULT_OPTS in
> make.conf (e.g. mine is:
>
> EMERGE_DEFAULT_OPTS="--keep-going --with-bdeps=y --autounmask-keep-masks 
> --ask --verbose --color=n"
>
> does only partly its job. Erratically, I'd say. You never know if it
> will or not remove color... A bug should be posted for that, but I have
> a partly broken system at this time...
>

That switch only handles the coloring of portage output. I suggested
using GCC_COLORS precisely because "--color=n" doesn't seem to
propagate to subcommands which do output coloring.

Another program you might want to disable output coloring for is
CMake, using CMAKE_COLOR_MAKEFILE=OFF.

Re: [gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[Miroslav Rovis]

On 170510-20:03-0400, Walter Dnes wrote:
> On Wed, May 10, 2017 at 01:35:24PM -0500, R0b0t1 wrote
> 
> > The option is "-fdiagnostics-color=never" or "-fno-diagnostics-color".
> > You can also set the environment variable GCC_COLORS to the empty
> > string. The latter is probably more useful in the context of portage.
> 
>   Thank you.  I successfully tried...
> 
> GCC_COLORS="" emerge icewm
Another tip to remember.

>   I suppose the next step is to add GCC_COLORS="" to make.conf.
> 
I wonder why sticking " --color=n" in the EMERGE_DEFAULT_OPTS in
make.conf (e.g. mine is:

EMERGE_DEFAULT_OPTS="--keep-going --with-bdeps=y --autounmask-keep-masks --ask 
--verbose --color=n"

does only partly its job. Erratically, I'd say. You never know if it
will or not remove color... A bug should be posted for that, but I have
a partly broken system at this time...

Regards!
-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

Re: [gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[Walter Dnes]

On Wed, May 10, 2017 at 01:35:24PM -0500, R0b0t1 wrote

> The option is "-fdiagnostics-color=never" or "-fno-diagnostics-color".
> You can also set the environment variable GCC_COLORS to the empty
> string. The latter is probably more useful in the context of portage.

  Thank you.  I successfully tried...

GCC_COLORS="" emerge icewm

  I suppose the next step is to add GCC_COLORS="" to make.conf.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[R0b0t1]

On Wed, May 10, 2017 at 1:29 PM, Walter Dnes  wrote:
>   Splitting away from the main GCC 6.3.0 thread, because this is a
> tangential issue.  The GCC 6.3.0 build output is cutsie/wootsie with
> lots of colour... "because teh shiney".  Unfortunately, it absolutely
> sucks for reading build logs giving stuff like...
>
> ^[[01m^[[Kicesh.cc:249:1:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Knarrowing 
> conversion of '^[[01m^[[K4294967295ul^[[m^[[K' from '^[[01m^[[Klong unsigned 
> int^[[m^[[K' to '^[[01m^[[Klong int^[[m^[[K' inside { } 
> [^[[01;31m^[[K-Wnarrowing^[[m^[[K]
>  ^[[01;31m^[[K}^[[m^[[K;
>  ^[[01;31m^[[K^^[[m^[[K
> ^[[01m^[[Kicesh.cc:261:1:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Knarrowing 
> conversion of '^[[01m^[[K4294967295ul^[[m^[[K' from '^[[01m^[[Klong unsigned 
> int^[[m^[[K' to '^[[01m^[[Klong int^[[m^[[K' inside { } 
> [^[[01;31m^[[K-Wnarrowing^[[m^[[K]
>  ^[[01;31m^[[K}^[[m^[[K;
>  ^[[01;31m^[[K^^[[m^[[K
>
>   I tried "emerge --color=n icewm", but that doesn't help.  Any ideas?
>
> --
> Walter Dnes 
> I don't run "desktop environments"; I run useful applications
>

The option is "-fdiagnostics-color=never" or "-fno-diagnostics-color".
You can also set the environment variable GCC_COLORS to the empty
string. The latter is probably more useful in the context of portage.

[gentoo-user] How do I turn off ansi (colour) codes in GCC 6.3.0 ?

[Walter Dnes]

  Splitting away from the main GCC 6.3.0 thread, because this is a
tangential issue.  The GCC 6.3.0 build output is cutsie/wootsie with
lots of colour... "because teh shiney".  Unfortunately, it absolutely
sucks for reading build logs giving stuff like...

^[[01m^[[Kicesh.cc:249:1:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Knarrowing 
conversion of '^[[01m^[[K4294967295ul^[[m^[[K' from '^[[01m^[[Klong unsigned 
int^[[m^[[K' to '^[[01m^[[Klong int^[[m^[[K' inside { } 
[^[[01;31m^[[K-Wnarrowing^[[m^[[K]
 ^[[01;31m^[[K}^[[m^[[K;
 ^[[01;31m^[[K^^[[m^[[K
^[[01m^[[Kicesh.cc:261:1:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Knarrowing 
conversion of '^[[01m^[[K4294967295ul^[[m^[[K' from '^[[01m^[[Klong unsigned 
int^[[m^[[K' to '^[[01m^[[Klong int^[[m^[[K' inside { } 
[^[[01;31m^[[K-Wnarrowing^[[m^[[K]
 ^[[01;31m^[[K}^[[m^[[K;
 ^[[01;31m^[[K^^[[m^[[K

  I tried "emerge --color=n icewm", but that doesn't help.  Any ideas?

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications