don't hardcode python2.6 in bindings/python/Makefile.am

[Evgeni Golov]

Hi,

while trying to bring libindicate to Debian, I stumbled over the following bug.
In configure.ac, you check for python >= 2.3.5, so any py2.4, 2.5, 2.6 etc would be fine...
But in bindings/python/Makefile.am you write:
 _indicate_la_LDFLAGS = -module -avoid-version -export-symbols-regex init_indicate -lpyglib-2.0-python2.6 -lpython2.6

That produces funny results when /usr/bin/python is NOT 2.6.x (like it's on Debian: 2.5.5).
Like: built with py2.5, linked with py2.6, installed to /usr/lib/python2.5...

Intermediate solution: export PYTHON=/usr/bin/python2.6 before building.

[Dennis Schridde (devurandom)]

This is even worse, if Python 2.6 is not installed. libindicate will fail to build miserably.

I propose attached patch.

[Dennis Schridde (devurandom)]

P.S: To properly fix this, configure.ac should not only guess the name of pyglib-2.0-python*, but also verify that this library actually exists. (And bail out early if it doesnt, with a useful error message.) In this sense the above patch is incomplete.

[Dennis Schridde (devurandom)]

Seems fixed in 0.4.91

[Dennis Schridde (devurandom)]

In fact it is not. :( Please reopen!

Attached patch improves detection of the Python version and its libraries.
The problem with the current situation in 0.4.91 is that it assumes python-config is named python$VERSION-config, which is not always true. A better solution is thus to let pkg-config figure out everything.

[Dennis Schridde (devurandom)]

Repeating my request to reopen from last comment.

The attached patch uses improved quoting and depends on the one attached to bug #643921 (optional-python).

[dcelasun (dcelasun)]

This also affects Arch Linux since /usr/bin/python2 (/usr/bin/python is Python 3!) points to python 2.7.x.