FS#22187 - [colorgcc] no color

Attached to Project: Community Packages
Opened by Francesco (nwoki) - Wednesday, 22 December 2010, 14:34 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 05 January 2011, 06:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Eric Belanger (Snowman)
Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Output of make and/or gcc compilation is not colorized anymore

Additional info:
* package version(s)
community/colorgcc 1.3.2-6
core/gcc 4.5.1-2
core/gcc-libs 4.5.1-2

* config and/or log files etc.

#
# colorgcc configuration file
#
# $Id: colorgccrc,v 1.1.1.1 1999/04/25 15:24:03 jamoyers Exp $
#
# This file should be named $HOME/.colorgccrc
#
#
# The following groups of attributes may be combined for a given color:
#
# clear black on_black
# reset red on_red
# bold green on_green
# underline yellow on_yellow
# underscore blue on_blue
# blink magenta on_magenta
# reverse cyan on_cyan
# concealed white on_white
#
# For example, srcColor: bold cyan on_yellow
#

# gccVersion: if defined, append "-<gccVersion>" to the compiler paths
# defined hereunder. Otherwise, those paths remains as is set
# gccVersion: 4.1.1

# Define the paths to the actual location of the various compilers.
# (Currently, colorgcc only understands these: g++ gcc c++ cc g77 f77 gcj)
g++: /usr/bin/g++
gcc: /usr/bin/gcc
c++: /usr/bin/g++
cc: /usr/bin/gcc
g77: /usr/bin/g77
f77: /usr/bin/g77
gcj: /usr/bin/gcj

# Don't do color if our terminal type ($TERM) is one of these.
# (List all terminal types on one line, seperated by whitespace.)
nocolor: dumb emacs

# Text between ` and ' is usually source code.
srcColor: bold cyan

# Text other than a warning or error.
introColor: reset

# Warnings and errors both have similar formats:
# filename:999:Message
# Each field may be assigned a different color.

# Warnings
warningFileNameColor: reset
warningNumberColor: blue
warningMessageColor: yellow

# Errors
errorFileNameColor: reset
errorNumberColor: blue
errorMessageColor: bold red

# Possible translations, if you use localized compiler.
# (List all translations on one line, seperated by whitespace.)
warningTranslations:
errorTranslations:



Steps to reproduce:

simply compile any g++ program
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 05 January 2011, 06:11 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#22279 
Comment by Jelle van der Waa (jelly) - Wednesday, 22 December 2010, 20:41 GMT
this is probably a bug upstream, i don't have the issue here. Please report it upstream.
Comment by Francesco (nwoki) - Sunday, 02 January 2011, 18:08 GMT
SOLVED:
I think there were some errors during the "build" process for the colorgcc package. I had to create symlinks in my "/usr/local/bin" folder to call colorgcc during compilation.

Here is the forum post: https://bbs.archlinux.org/viewtopic.php?pid=867368
Comment by Jelle van der Waa (jelly) - Monday, 03 January 2011, 09:14 GMT
Since setting the CC VAR also works, i would rather edit the post install to warn users about it. Symlinking is ugly in my opinion.

Example
export CC=/usr/bin/colorgcc

Loading...