Comment 16 for bug 345208

The issue stems from libboost_python.so not being linked as part of the _PythonMagick.so build process. Starting Python like:

LD_PRELOAD=/usr/lib/libboost_python.so python
Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import PythonMagick
>>>

works fine. The configure script seems to skip adding -lboost_python to the LDFLAGS because when checking for libboost_python, the test program that it compiles doesn't include -lpython2.6 -- and libboost_python doesn't link to libpython2.6 already. So lots of undefined symbols, the test program fails, and the configure script decides libboost_python doesn't exist.

(But it's a twisty maze of buildscripts and so I ultimately didn't figure out what magic line needed changed...)