Check attached build log, latest ~arch version of python moved the static library to /usr/$libdir (and still it shouldn't link to the static version!)
Created attachment 194123 [details] Build log
This holds back stabilisation of Python 2.6
Christian, that doesn't really feel right.. on my stable (amd64) chroot: yamato / # qlist python | grep libpy /usr/lib64/libpython2.5.so.1.0 /usr/lib64/libpython2.5.a /usr/lib64/libpython2.5.so yamato / # qlist -I -v python app-admin/eselect-python-20090606 app-admin/python-updater-0.5 dev-lang/python-2.5.4-r3
(In reply to comment #3) > Christian, that doesn't really feel right.. on my stable (amd64) chroot: I don't really understand what you are trying to tell me.
That the cause of the problem (moved libpython.a) is already present in the stable version of Python, at least on amd64, so I'm not sure how this is holding up Python 2.6.
(In reply to comment #5) > That the cause of the problem (moved libpython.a) is already present in the > stable version of Python, at least on amd64, so I'm not sure how this is > holding up Python 2.6. It should have held up Python 2.5 already...anyway, I just stumbled about it for Python 2.6.
probably fixed by using python-config. reopen if not.