As first reported in $URL, dev-python/pygobject has a top level Makefile.am that overwrites TMPDIR with a value that is not an absolute path. As a result, distcc fails to find a usable temporary directory, and reverts to compiling locally. I submitted a patch to upstream, which was committed and can be viewed at <http://git.gnome.org/browse/pygobject/commit/?id=4e2efa91d101bf755739e1cca8eee41eb0ad20fd>. Please consider applying this patch to existing Gentoo ebuilds. Since the problem does not impact the installed code, no revision bump is needed.
This also causes compilation to fail on Interix (gentoo prefix), where settinng TMPDIR to anything but a Windows-style "C:\whatever" file-path is disastrous.
Created attachment 222669 [details, diff] rename TMPDIR variable to something less dangerous This patch will fix the problem until the patch trickles down from upstream. Even if this code were accidentally left in portage thereafter, it would harmlessly rename EGG_TMPDIR to EGG_EGG_TMPDIR.
I'd rather have a Makefile.am patch. I'll try to look at this tonight.
(In reply to comment #3) > I'd rather have a Makefile.am patch. I'll try to look at this tonight. Do you mean you would prefer a .patch file over a change made with sed? Such a patch was committed upstream, and is linked in comment #0. The 'patch' link in the resulting Git view CGI <http://git.gnome.org/browse/pygobject/patch/?id=4e2efa91d101bf755739e1cca8eee41eb0ad20fd> will generate a patch that should be suitable for application via epatch.
Just fixed in 2.20.0 without a bump, thanks to the report and the patch
