During the last days PYTHON_TARGETS was changed in default profile. It added python3_3 - and removed python3_2. I really would have expected a news item for this! The problem: This update did not change the current active python, leading to issues with pythonmagick: It builds against the current active python (still python3.2), but boost was built without python3.2-support (due to PYTHON_TARGETS change), so pythonmagick fails during linktime, linking against nonexistent libboost_python-3.2: /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lboost_python-3.2 eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 * [3] python3.3 eix boost [I] dev-libs/boost Available versions: 1.49.0-r2 1.52.0-r6(0/1.52) ~1.53.0(0/1.53) [M]~1.54.0(0/1.54) [M]~1.55.0(0/1.55.0)^t {debug doc icu mpi +nls python static-libs +threads tools PYTHON_TARGETS="python2_6 python2_7 python3_2 python3_3"} Installed versions: 1.52.0-r6(16:09:35 05.12.2013)(icu mpi nls python threads -debug -doc -static-libs -tools PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2")
Created attachment 365016 [details] build log
Not migrated to python-r1.eclass
pythonmagick-0.9.10 was ported to python-r1 -> closing.