[Users] [Bug 2770] Python plugin is linked against libpythonXY.so instead of libpythonXY.so.1.0

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Sat Nov 3 21:01:27 CET 2012


--- Comment #4 from Holger Berndt  2012-11-03 21:01:26 ---
No, setting the variable correctly should do the trick. However, I'm not gonna
merge hardcoded .so numbers upstream.

Some time ago (when hearing about the same issue in Debian [1]), I thought it
would be nice if the plugin detected the correct .so.x.y file via
self-inspection at runtime (since it's linked against it already). I had a
quick look at ldd's source code to see how it works, and quickly gave up on the
idea - it's ultra platform-specific.

I think the second best solution would be to resolve the symlink at build time.
"readlink -f" seems to have portability problems, too. But since we have a
python dependency anyways, setting the variable to something along the lines of

python -c 'import os.path; print os.path.realpath($PYTHON_SHARED_LIB)'

should work.

If you could provide a patch and check if it works for you, that would be
appreciated. We have a release comming up, though, so if you don't have time
during the next couple of days, I'll probably do it myself.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644582

Configure bugmail: http://www.thewildbeast.co.uk/claws-mail/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Users mailing list