Somebody should mask colorgcc or let find it out where the gcc executable resides. Maybe by doing which gcc or some other mechanism. CCing blizzy and azarah as they last changed the affected ebuilds. regs, Chris
This is fixed in gcc-config-1.2.7 and colorgcc-1.3.2-r2. Do note that you need to source /etc/profile if you just merged those two for it to work. For portage however, this should be transparent ...
Fixed.
The current fix seems to only work if colorgcc was already emerged before gcc-config. To emerge colorgcc on an uptodate system where it was not already emerged, I have to do: # emerge colorgcc # gcc-config i686-pc-linux-gnu-3.2.1 # emerge colorgcc because colorgcc is using CCBINPATH environment variable that was defined by gcc-config *if* /usr/bin/colorgcc was around when gcc-config was emerged... or I could be mistaken.
