please env.d # ACCEPT_KEYWORDS=~x86 emerge python-fchksum Calculating dependencies ...done! >>> emerge (1 of 1) dev-python/python-fchksum-1.7.1 to / >>> md5 src_uri ;-) python-fchksum-1.7.1.tar.gz >>> Unpacking source... >>> Unpacking python-fchksum-1.7.1.tar.gz to /usr/local/portage/portage/python-fchksum-1.7.1/work >>> Source unpacked. ['setup.py', 'build'] running build running build_ext building 'fchksum' extension creating build creating build/temp.linux-i686-2.2 colorgcc -DNDEBUG -fPIC -I/usr/include/python2.2 -c fchksum.c -o build/temp.linux-i686-2.2/fchksum.o -march=athlon-mp -O2 -ftracer -ffast-math -pipe -fomit-frame-pointer After which it just sits there indefinately. If I call colorgcc form the command line it works: please env.d # colorgcc gcc: no input files but interestingly, if I call /usr/bin/colorgcc it hangs just as in the ebuild. I'd be happy to build without color, but poking around the ebuild and the source work directory I could not find any way to tell it *not* to use colorgcc. Reproducible: Always Steps to Reproduce: 1. 2. 3. please env.d # emerge info Portage 2.0.49-r7 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r3, 2.4.22) ================================================================= System uname: 2.4.22 i686 AMD Athlon(tm) MP 2000+ ccache version 2.3 [disabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-mp -O2 -ftracer -ffast-math -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/local/portage/distfiles" FEATURES="sandbox autoaddcvs fixpackages colorgcc" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/usr/local/portage" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/ebuilds" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm cups foomaticdb mad mikmod nls xml2 gdbm slang bonobo ruby libwww motif cdr X 3dnow mmx directfb sse dga opengl xv fbcon kde qt qtmt arts tcltk aalib imlib ncurses readline sdl svga lcms gif jpeg png tiff gd avi mpeg quicktime esd gtk gtk2 -gnome alsa ggi dvd xmms oggvorbis encode pam ssl crypt tcpd mozilla spell truetype xml pdflib plotutils tetex guile perl python libg++ atlas pic berkdb mysql postgres odbc samba gpm zlib java ppds threads"
the answer for now is dont mess around with colorgcc + portage *** This bug has been marked as a duplicate of 2679 ***
SpanKY: Note that giggles1 did ask how to turn off colorgcc in this build process, so it sounds like this is an unintentional colorgcc interaction. It's very strange that "colorgcc" even comes up in the output on the compile lines. I'm not very familar with the "python setup.py build" process, though, so if there's something to do with colorgcc secreted in there, that might explain things, but it didn't look like it to me. For instance, I tried reproducing the problem by setting CC to colorgcc and it didn't cause the build process to switch from using gcc explicitly. giggles1: You might try installing colorgcc 1.3.2-r4 (currently masked) to see if that makes the problem go away. Also, look around and see if the /usr/bin/wrappers dir is on the PATH in the global environment files, and if so, try removing it.
i missed the unintentional factor ... /usr/bin/wrappers does not apply here since colorgcc uses /usr/lib/colorgcc/bin for its wrappers dir ... but the same idea applies, make sure your PATH doesnt have colorgcc in it ... also check the CC and CXX env variables to make sure they arent set to colorgcc
Hi, I had added \usr\lib\colorgcc\bin to my path (I thought, on the urging of the last colorgcc ebuild instructions..). However, even if I remove it, the problem persists: please env.d # echo $PATH /bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3:/opt/intel/compiler70/ia32/bin:/opt/Acrobat5:/usr/X11R6/bin:/opt/sun-j2sdk-1.4.1/bin:/opt/sun-j2sdk-1.4.1/jre/bin:/usr/qt/3/bin:/usr/kde/3.1/sbin:/usr/kde/3.1/bin:/usr/qt/2/bin:/opt/vmware/bin please env.d # echo $CC gcc please env.d # ACCEPT_KEYWORDS=~x86 emerge python-fchksum ... <same result> BTW I do already have colorgcc-1.3.2-r4 installed. I also assumed this must be hardwired somewhere deep in setup.py, etc. but I have not been able to find it. I say this because even if I *unmerge* colorgcc I still get: please env.d # ACCEPT_KEYWORDS=~x86 emerge python-fchksum Calculating dependencies ...done! >>> emerge (1 of 1) dev-python/python-fchksum-1.7.1 to / >>> md5 src_uri ;-) python-fchksum-1.7.1.tar.gz >>> Unpacking source... >>> Unpacking python-fchksum-1.7.1.tar.gz to /usr/local/portage/portage/python-fchksum-1.7.1/work >>> Source unpacked. ['setup.py', 'build'] running build running build_ext building 'fchksum' extension creating build creating build/temp.linux-i686-2.2 colorgcc -DNDEBUG -fPIC -I/usr/include/python2.2 -c fchksum.c -o build/temp.linux-i686-2.2/fchksum.o -march=athlon-mp -O2 -ftracer -ffast-math -pipe -fomit-frame-pointer unable to execute colorgcc: No such file or directory error: command 'colorgcc' failed with exit status 1 !!! ERROR: dev-python/python-fchksum-1.7.1 failed. !!! Function src_compile, Line 20, Exitcode 1 !!! (no error message) and just to double check: please env.d # env |grep color please env.d # env |grep wrapper please env.d # very strange. Any insights appreciated.
try logging in/out ... try `env-update ; source /etc/profile` ... try in a different terminal ;)
Same result. 'grep' confirms that there is nothing in /etc/profile (or all of \etc\*) or /etc/env.d/* that mentions colorgcc or wrapper. Theres nothing in the output from 'env' either, and CC has been exported to 'gcc' as well. This is somewhere in the setup.py business, there's nowhere else it could be.
FWIW re-emerging Python fixes this problem.
