1 |
Heiko Wundram <heiko@××××××.net> writes: |
2 |
|
3 |
> On Wed, 15 Jul 2009 16:13:01 -0500, Harry Putnam <reader@×××××××.com> |
4 |
> wrote: |
5 |
>> <snip> |
6 |
>> So far I haven't found any instance of i486 files remaining on the |
7 |
>> system... what else might evoke that output? |
8 |
> |
9 |
> As I said: some Python makefile retains the reference to the (former) i486 |
10 |
> compiler. That Makefile is used when building packages using distutils |
11 |
> (that's what's happening here). If remerging Python itself didn't help, how |
12 |
> about grepping /usr/lib/python2.6 for "i486", and replacing the matching |
13 |
> string by hand? |
14 |
> |
15 |
> grep -R "i486" /usr/lib/python2.6 |
16 |
> |
17 |
> On my system (i686), it's /usr/lib/python2.6/config/Makefile that matches. |
18 |
> And that should also be what's used by distutils. |
19 |
|
20 |
Yup... I didn't quite follow your first post about that. And assumed |
21 |
the re-emerge of python under i686 would fix it. |
22 |
|
23 |
But after editing multiple occurrances of i486 in |
24 |
/usr/lib/python2.6/config/Makefile ... pycairo now emerges with no |
25 |
errors.. thanks. |