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
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
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
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
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
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
6 matches
Mail list logo