1 |
On Dienstag 14 Juli 2009, Harry Putnam wrote: |
2 |
> Volker Armin Hemmann <volkerarmin@××××××××××.com> writes: |
3 |
> |
4 |
> |
5 |
> [...] |
6 |
> |
7 |
> >> i486-pc-linux-gnu-gcc: No such file or directory error: command |
8 |
> >> 'i486-pc-linux-gnu-gcc' failed with exit status 1 |
9 |
> >> [...] |
10 |
> > |
11 |
> > did you run fix-libtool.sh? |
12 |
> |
13 |
> Doing so failed to help in any way. |
14 |
> |
15 |
> root # fix_libtool_files.sh `gcc -dumpversion` --oldarch i486-pc-linux-gnu |
16 |
> * Scanning libtool files for hardcoded gcc library paths... |
17 |
> * [1/5] Scanning /lib ... |
18 |
> * [2/5] Scanning /usr/lib ... |
19 |
> * [3/5] Scanning //usr//lib/opengl/xorg-x11/lib ... |
20 |
> * [4/5] Scanning /usr/i686-pc-linux-gnu/lib ... |
21 |
> * [5/5] Scanning /usr/local/lib ... |
22 |
> |
23 |
> Looks like nothing was found. |
24 |
> |
25 |
> reemerge pycairo fails with same error |
26 |
> |
27 |
> Heiko Wundram <heiko@××××××.net> writes: |
28 |
> |
29 |
> |
30 |
> [...] |
31 |
> |
32 |
> >> unable to execute i486-pc-linux-gnu-gcc: No such file or directory |
33 |
> >> error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 |
34 |
> >> [...] |
35 |
> > |
36 |
> > Re-merge python. Python keeps the compiler that was used to compile it in |
37 |
> > a separate "Makefile" that's used to compile Python packages (with |
38 |
> > distutils), and that's what you're hitting here (as you haven't updated |
39 |
> > that). |
40 |
> |
41 |
> That went off without error, but then going back to update world fails |
42 |
> at pycairo with same error message. |
43 |
|
44 |
you could grep for i486-pc-linux-gnu-gcc |