The ebuild uses gcc explicitly instead of ${CC:-gcc}. While those are trivial fixes, the missingos python module's setup script does not respect the CC env var, which seems to be a bug with python's distutils modules (or I'm missing something really obvious). To reproduce, `CC=i686-pc-linux-gnu-gcc emerge sys-apps/portage` and notice that all compiles still take place with gcc. To fix the ebuild, change references to gcc as suggested above. The python setup fix eludes me; however, you'll be able to tell when you finally get it right from the build output. You don't even need to use distcc to test and fix this.
seems to be fixed.
