public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bluetooth.developer at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/36150] colorize output of gcc Date: Mon, 20 Jan 2014 02:41:00 -0000 [thread overview] Message-ID: <bug-36150-4-GFj332Dcx5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-36150-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 bluetooth.developer at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bluetooth.developer at gmail dot c | |om --- Comment #17 from bluetooth.developer at gmail dot com --- Alternatively you could use GilCC which is a tool to colorize GCC output in real time. Just in case you cannot use GGC version 4.9 you still can use GilCC. here is the download link: http://www.onlysolutionssoftware.com/gilcc/
next prev parent reply other threads:[~2014-01-20 2:41 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-36150-4@http.gcc.gnu.org/bugzilla/> 2010-10-02 17:04 ` pinskia at gcc dot gnu.org 2010-10-02 17:52 ` manu at gcc dot gnu.org 2010-10-02 19:51 ` manu at gcc dot gnu.org 2011-03-16 14:49 ` manu at gcc dot gnu.org 2013-04-14 17:57 ` manu at gcc dot gnu.org 2014-01-20 2:41 ` bluetooth.developer at gmail dot com [this message] 2008-05-06 9:36 [Bug other/36150] New: " pva at gentoo dot org 2008-05-06 15:28 ` [Bug other/36150] " pinskia at gcc dot gnu dot org 2008-05-06 17:28 ` esigra at gmail dot com 2008-05-06 17:35 ` pinskia at gcc dot gnu dot org 2008-05-06 17:38 ` pinskia at gcc dot gnu dot org 2008-05-06 18:08 ` pva at gentoo dot org 2008-05-06 18:41 ` esigra at gmail dot com 2008-05-06 21:29 ` brian at dessent dot net 2008-05-06 21:56 ` esigra at gmail dot com 2008-05-06 21:58 ` pinskia at gcc dot gnu dot org 2008-05-06 22:07 ` brian at dessent dot net 2008-05-07 6:55 ` pva at gentoo dot org
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=bug-36150-4-GFj332Dcx5@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).