From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] GDB testsuite: Suppress GCC's colored output
Date: Fri, 04 Aug 2017 12:19:00 -0000 [thread overview]
Message-ID: <3bec6ebd5ee77f9d5b134c1dda6b62ea@polymtl.ca> (raw)
In-Reply-To: <86h8xn3833.fsf@gmail.com>
On 2017-08-04 13:06, Yao Qi wrote:
> Andreas Arnez <arnez@linux.vnet.ibm.com> writes:
>
> Hi Andreas,
>
>> + # Stop the compiler from producing colored output.
>> + setenv GCC_COLORS ""
>> +
>
> This doesn't work for remote host. How about passing option
> -fno-color-diagnostics to compiler which supports that option? Both
> gcc
> (4.9 and later) and clang has this option.
My gcc (5.4) doesn't recognize it:
$ gcc -fno-color-diagnostics test.c
gcc: error: unrecognized command line option ‘-fno-color-diagnostics’
It knows about -fdiagnostics-color=never however, which clang seems to
recognize as well. It would be nice however not to restrict the
compiler version used for testing just for this. Can we write a small
proc that checks if the compiler recognizes that flag and only include
it if it does?
Simon
next prev parent reply other threads:[~2017-08-04 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 17:35 Andreas Arnez
2017-08-02 20:22 ` Simon Marchi
2017-08-03 11:13 ` Andreas Arnez
[not found] ` <86h8xn3833.fsf@gmail.com>
2017-08-04 12:19 ` Simon Marchi [this message]
2017-08-04 13:00 ` Yao Qi
2017-08-08 18:29 ` Andreas Arnez
2017-08-09 10:01 ` Simon Marchi
2017-08-09 10:29 ` Yao Qi
2017-08-14 18:32 ` Andreas Arnez
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=3bec6ebd5ee77f9d5b134c1dda6b62ea@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox