| 1 |
Alex Schuster <wonko@×××××××××.org> [10-06-20 15:16]: |
| 2 |
> meino.cramer@×××.de writes: |
| 3 |
> |
| 4 |
> > Tried that...python3.1 compiles fine, setuptools failed. |
| 5 |
> > |
| 6 |
> > And now? |
| 7 |
> |
| 8 |
> How about putting dev-python/setuptools into |
| 9 |
> /etc/portage/package.keywords, and trying to emerge 0.6.13? |
| 10 |
> |
| 11 |
> Wonko |
| 12 |
> |
| 13 |
|
| 14 |
Hi, |
| 15 |
|
| 16 |
thanks for your posting, Wonko! :) |
| 17 |
|
| 18 |
Is there any Changelog-issue in that version, that says anything |
| 19 |
related to the compilation problem? |
| 20 |
|
| 21 |
I tried to re-emerge setuptools 0.6.10 and it fails the same way. |
| 22 |
So I believe (=not knowing) that this problem is caused by something |
| 23 |
outside setuptools, which gets screwed up. |
| 24 |
|
| 25 |
Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10 |
| 26 |
(current version) is gone and cannot get back due to the same problem |
| 27 |
(see above). And then I have a "unstable" version, which may pull in |
| 28 |
other unstable versions of something else, which pull in.... |
| 29 |
|
| 30 |
This way I have corrupted my last installed gentoo system... |
| 31 |
|
| 32 |
Best regards, |
| 33 |
mcc |
Archives