| 1 |
Hey Wonko, |
| 2 |
thanks for your answer... |
| 3 |
|
| 4 |
I played around and found that there's a place in the Makefile, where |
| 5 |
various PATHs are set, but not LD_LIBRARY_PATH, so I set it myself, and |
| 6 |
continues by hand and it worked.... |
| 7 |
I already wanted to file a bug, so I ran emerge again to get the build |
| 8 |
logs again, but then emerge ran fine... |
| 9 |
|
| 10 |
So... Nevermind! ;) |
| 11 |
|
| 12 |
Am 14.09.2011 02:52, schrieb Alex Schuster: |
| 13 |
> Moritz Schlarb writes: |
| 14 |
> |
| 15 |
> |
| 16 |
>> /usr/bin/install -c -m 644 pyconfig.h |
| 17 |
>> /var/tmp/portage/dev-lang/python-2.5.4-r4/image//usr/include/python2.5/pyconfig.h |
| 18 |
>> emake failed |
| 19 |
>> * ERROR: dev-lang/python-2.5.4-r4 failed (install phase): |
| 20 |
>> * emake altinstall maninstall failed |
| 21 |
> [...] |
| 22 |
>> Doesn't make much sense to me, failing at installing to |
| 23 |
>> python2.5-specific directories... I would investigate further, but I |
| 24 |
>> don't know how to make portage tell me more about the error that |
| 25 |
>> occured! But I'm eager to learn, would be great if someone could tell |
| 26 |
>> me where to look for debugging infos. |
| 27 |
> |
| 28 |
> Look at yout build.log, line 942, a libpython2.5.so.1.0 cannot be found. |
| 29 |
> I don't know why, and I have no time to look further right now. I'd try |
| 30 |
> again with MAKEOPTS=-j1 in case something was executed out of order and in |
| 31 |
> parallel, but that's just a tip, no idea if this might help. Look |
| 32 |
> in /var/tmp/portage/dev-lang/python-2.5.4-r4/image/ and check if this |
| 33 |
> library exists, and maybe try to do by hand what failed in the build log. |
| 34 |
> |
| 35 |
> Sorry, my time is up, |
| 36 |
> |
| 37 |
> Wonko |
| 38 |
> |
| 39 |
> |
| 40 |
|
| 41 |
-- |
| 42 |
Moritz Schlarb |
Archives