If your Python was built with i386-pc-linux-gnu-gcc, try re-emerging Python. Python has the compiler it was built with hard coded as the compiler to use.
Regards Frank On Thu, 2005-10-06 at 11:05 +0200, Christian Fischer wrote: > Hi all. > > I've some trouble with emerging dev-python/pyopengl. > I get "gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" > > I've done the following: > > # gcc-config -l > [1] i686-pc-linux-gnu-3.3.6 * > [2] i686-pc-linux-gnu-3.3.6-hardened > [3] i686-pc-linux-gnu-3.3.6-hardenednopie > [4] i686-pc-linux-gnu-3.3.6-hardenednopiessp > [5] i686-pc-linux-gnu-3.3.6-hardenednossp > > # fix_libtool_files.sh 3.3 --oldarch i386-pc-linux-gnu > * Scanning libtool files for hardcoded gcc library paths... > * [1/6] Scanning /lib ... > * [2/6] Scanning /usr/lib ... > * FIXING: /usr/lib/libkwmf.la ...[] > [...] > * [3/6] Scanning /usr/i386-pc-linux-gnu/lib ... > * [4/6] Scanning /usr/kde/3.4/lib ... > FIXING: /usr/kde/3.4/lib/libkabc_ldapkio.la ...[] > [...] > * [5/6] Scanning /usr/local/lib ... > * [6/6] Scanning /usr/qt/3/lib ... > > # env-update && source /etc/profile > > But that don't help. > > # emerge dev-python/pyopengl > [...] > SWIG Version 1.3.21 > Copyright (c) 1995-1998 > University of Utah and the Regents of the University of California > Copyright (c) 1998-2003 > University of Chicago > Compiled with g++ [i686-pc-linux-gnu] > [...] > running build_py > i386-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 > -march=pentium3 -fomit-frame-pointer -pipe -fPIC -DGLX_PLATFORM > -I/usr/include -I/usr/local/include -I/usr/X11R6/include > -I/usr/lib/tk8.4/include -Isrc/gle/src -I/usr/include/python2.3 -c > _configtest.c -o _configtest.o > gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" > [...] > > Please can you give me some hints how to solve this problem? > > Christian -- [email protected] mailing list
