colorgcc patch

Mario Schwalbe schwalbe at
Thu Nov 5 15:28:12 GMT 2009


I'm using colorgcc 1.3.2 (Ubuntu package version

While I generally like this tool, I think 2 issues are somewhat

(1) One has to define all different kinds of compiler binaries
    (cpp, gcc, cc, c++, g++, ...) of all versions (3.3, 3.4, 4.0, ...)
    explicitly in its configuration file. I know the 'gccVersion'
    option, but it isn't of much use if using several different
    versions at once.
(2) colorgcc silently defaults to a default binary (/usr/bin/gcc, ...),
    which is the standard version on a platform, if nothing else
    is configured.

This took me several hours of searching, because I silently compiled
using the wrong compiler, that was already known to break builds.

So why doesn't colorgcc just search the compiler binary itself,
skipping those that are again symlinks to itself? This way one doesn't
have to configure the paths in colorgcc anymore and can fully rely on
the usual environment variables and build systems.

The attached patch tries to accomplish that and also lets the script die,
if it doesn't find a compiler.


 Wo das Chaos auf die Ordnung trifft, gewinnt meist das Chaos,
 weil es besser organisiert ist.
     - Friedrich Nietzsche -

    _____    ________
   /     \  /   ____/  Mario Schwalbe
  /  \ /  \ \____  \
 /    Y    \/       \  eMail: schwalbe at,
 \____|__  /______  /         s4700588 at
         \/       \/

          key ID: 7DA9 DAFF
 key fingerprint: 2979 AA20 4A93 B527 90CC  45E5 4B28 511A 7DA9 DAFF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: colorgcc-search-binary-2009-11-05.patch
Type: text/x-patch
Size: 1976 bytes
Desc: not available
Url : 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : 

More information about the Ubuntu-motu mailing list