On Dienstag 14 Juli 2009, Harry Putnam wrote: > Volker Armin Hemmann <volkerar...@googlemail.com> writes: > > > [...] > > >> i486-pc-linux-gnu-gcc: No such file or directory error: command > >> 'i486-pc-linux-gnu-gcc' failed with exit status 1 > >> [...] > > > > did you run fix-libtool.sh? > > Doing so failed to help in any way. > > root # fix_libtool_files.sh `gcc -dumpversion` --oldarch i486-pc-linux-gnu > * Scanning libtool files for hardcoded gcc library paths... > * [1/5] Scanning /lib ... > * [2/5] Scanning /usr/lib ... > * [3/5] Scanning //usr//lib/opengl/xorg-x11/lib ... > * [4/5] Scanning /usr/i686-pc-linux-gnu/lib ... > * [5/5] Scanning /usr/local/lib ... > > Looks like nothing was found. > > reemerge pycairo fails with same error > > Heiko Wundram <he...@xencon.net> writes: > > > [...] > > >> unable to execute i486-pc-linux-gnu-gcc: No such file or directory > >> error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 > >> [...] > > > > Re-merge python. Python keeps the compiler that was used to compile it in > > a separate "Makefile" that's used to compile Python packages (with > > distutils), and that's what you're hitting here (as you haven't updated > > that). > > That went off without error, but then going back to update world fails > at pycairo with same error message.
you could grep for i486-pc-linux-gnu-gcc
