| 1 |
Am 09.01.2014 12:29, schrieb Neil Bothwick: |
| 2 |
> On Thu, 09 Jan 2014 11:16:01 +0100, Stefan G. Weichinger wrote: |
| 3 |
> |
| 4 |
>> I only have python 2.7 / 3.2 / 3.3 now installed. |
| 5 |
> |
| 6 |
> Bear n mind that portage will stick with python2, whatever your |
| 7 |
> eselect settings, unless you emerged it with the python3 USE flag. |
| 8 |
|
| 9 |
Yes. |
| 10 |
|
| 11 |
What I did now: went back to gcc-4.4.4-r2 (built in 2010) and rebuilt |
| 12 |
both dev-lang/python:2.7 and dev-lang/python:3.2 |
| 13 |
|
| 14 |
So I should have python built against the current unpacked glibc-2.16, |
| 15 |
right? |
| 16 |
|
| 17 |
Now I could retry to upgrade to glibc-2.17 ... and see if I hit that |
| 18 |
missing eutils.eclass again. |
Archives