All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] infra/ccache: avoid color diagnostics with GCC older than v4.9
Date: Sun, 12 Feb 2017 12:55:37 -0200 (BRST)	[thread overview]
Message-ID: <609383214.9983962.1486911337173.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20170212141425.GE11105@free.fr>

> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: buildroot at buildroot.org, "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>, arnout at mind.be,
> gustavo at zacarias.com.ar
> Sent: Sunday, February 12, 2017 12:14:25 PM
> Subject: Re: [PATCH v2] infra/ccache: avoid color diagnostics with GCC older than v4.9

> Carlos, All,
> 
> On 2017-02-12 09:33 -0200, Carlos Santos spake thusly:
>> Ensure that the GCC_COLORS environment variable is empty when calling
>> ccache. When GCC_COLORS is set, ccache passes '-fdiagnostics-color' to
>> GCC but this flag requires GCC v4.9 or later. Older versions complain
>> about the unrecognized command line option.
> 
> So, while fixing my own patch about the issue [0], I noticed that I was
> not even able to make it fail in the first place...
> 
> I'm using this defconfig, which uses a gcc-4.7:
> 
>    BR2_x86_i686=y
>    BR2_CCACHE=y
>    BR2_TOOLCHAIN_EXTERNAL=y
> 
> and Thomas reported he was also unable to reproduce the failure with:
> 
>    BR2_sh=y
>    BR2_sh4a=y
>    BR2_CCACHE=y
>    BR2_TOOLCHAIN_EXTERNAL=y
>    BR2_INIT_NONE=y
>    BR2_SYSTEM_BIN_SH_NONE=y
>    # BR2_PACKAGE_BUSYBOX is not set
>    BR2_PACKAGE_DEVMEM2=y
>    # BR2_TARGET_ROOTFS_TAR is not set
> 
> which also uses gcc-4.7.
> 
> Can you provide a reliable way to reproduce the issue, please?

What does "echo $GCC_COLORS" say? And remember that you must not
redirect the output to a file or pipe.

Carlos Santos (Casantos) - DATACOM, P&D
?Something must be done. This is something. Therefore we must do it.?
(from the BBC series ?Yes, Prime Minister?, ?Power to the people?)

  reply	other threads:[~2017-02-12 14:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 13:34 [Buildroot] [PATCH] infra/ccache: avoid color diagnostics with GCC older than v4.9 Carlos Santos
2017-02-11 15:38 ` Thomas Petazzoni
2017-02-12 10:08   ` Yann E. MORIN
2017-02-12 12:14     ` Thomas Petazzoni
2017-02-12 12:33       ` Yann E. MORIN
2017-02-12 12:59         ` Thomas Petazzoni
2017-02-12 13:08           ` Yann E. MORIN
2017-02-12 13:10             ` Thomas Petazzoni
2017-02-12 11:33 ` [Buildroot] [PATCH v2] " Carlos Santos
2017-02-12 12:34   ` Yann E. MORIN
2017-02-12 14:14   ` Yann E. MORIN
2017-02-12 14:55     ` Carlos Santos [this message]
2017-02-12 17:21       ` Yann E. MORIN
2017-02-12 17:22       ` Thomas Petazzoni
2017-02-12 17:28         ` Yann E. MORIN
2017-02-13 22:41     ` Carlos Santos
2017-02-14 16:48       ` Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=609383214.9983962.1486911337173.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.