| 1 |
Alan McKinnon wrote: |
| 2 |
> On Saturday 19 June 2010 18:06:58 meino.cramer@×××.de wrote: |
| 3 |
> |
| 4 |
>> David W Noon<dwnoon@××××××××.com> [10-06-19 18:00]: |
| 5 |
>> |
| 6 |
>>> On Sat, 19 Jun 2010 17:00:02 +0200, meino.cramer@×××.de wrote about Re: |
| 7 |
>>> |
| 8 |
>>> [gentoo-user] Re: Compilation aborted for setuptools-0.6.12: |
| 9 |
>>> |
| 10 |
>>>> walt<w41ter@×××××.com> [10-06-19 16:48]: |
| 11 |
>>>> |
| 12 |
>>> [snip] |
| 13 |
>>> |
| 14 |
>>> |
| 15 |
>>>>> Have you set eselect python to use python-3 instead of python-2? If |
| 16 |
>>>>> so, |
| 17 |
>>>>> try setting it back to python-2. |
| 18 |
>>>>> |
| 19 |
>>>> No, python 2.6 ist set according to the output of |
| 20 |
>>>> |
| 21 |
>>>> eselect python list |
| 22 |
>>>> |
| 23 |
>>>> python 3.1 is installed but not selected. |
| 24 |
>>>> |
| 25 |
>>>> What else can produce this compilation error? |
| 26 |
>>>> |
| 27 |
>>> Have you run python-updater? |
| 28 |
>>> |
| 29 |
>>> When new packages have Python components, they will build both 2.6 and |
| 30 |
>>> 3.1 modules if possible. This means that their dependencies also need |
| 31 |
>>> to have both 2.6 and 3.1 modules. You achieve this by running |
| 32 |
>>> python-updater; this can take several hours. |
| 33 |
>>> |
| 34 |
>> Hi Dave, |
| 35 |
>> |
| 36 |
>> wait...hopefully I understand this correctly, before I start to screw |
| 37 |
>> up my newly installed system... |
| 38 |
>> |
| 39 |
>> State 1 right after installing Gentoo: Pyton2.6 selected, installed |
| 40 |
>> and up. |
| 41 |
>> State 2 some days later while upateing python3.1 was offered but |
| 42 |
>> should *not* eselect python 3.1 since some older package are still |
| 43 |
>> not updated to work correctly with 3.1 |
| 44 |
>> State 3 setuptools seems to try to compile against 3.1 and failed. |
| 45 |
>> |
| 46 |
>> Now I should run python-updater to ... (scratching my head)? |
| 47 |
>> To update to python 3.1..but setuptools failed while compiling |
| 48 |
>> against python 3.1 |
| 49 |
>> |
| 50 |
>> It seems I myself feel a little screwed up,,, ;) |
| 51 |
>> |
| 52 |
>> ? |
| 53 |
>> |
| 54 |
>> Best regards, |
| 55 |
>> mcc |
| 56 |
>> |
| 57 |
> Did you miss the significance of this part? |
| 58 |
> |
| 59 |
> "This means that their dependencies also need to have both 2.6 and 3.1 |
| 60 |
> modules. You achieve this by running python-updater; this can take several |
| 61 |
> hours." |
| 62 |
> |
| 63 |
> |
| 64 |
|
| 65 |
Or if he doesn't really need python 3, he can just mask the thing until |
| 66 |
he does need it. Of course, he may have to run python-updater again or |
| 67 |
rebuild the same packages again to get them to not use python 3. |
| 68 |
|
| 69 |
Yep, making this stable hasn't confused anyone yet. o_O |
| 70 |
|
| 71 |
Dale |
| 72 |
|
| 73 |
:-) :-) |
Archives