koobs added the comment:
To clarify, the bug remains in all branches including default, but only 3.4+
use the .sh script, leaving 3.3, 3.2, 2.7 using the python implementation.
--
versions: +Python 3.6
___
Python tracker
koobs added the comment:
The attached patch courtesy of Jan Beich @ FreeBSD minimally mimics (in the
python version), the --ldflags output of the shell version of
python-config(.sh).
The ideal scenario of course would be to use the shell script across all
versions, as per revision
Maxim Egorushkin added the comment:
I encountered this issue when compiling gdb against my own build of Python 2.7
in a non-standard location. gdb could not locate libpython2.7.so.
The solution is to configure Python with LINKFORSHARED variable which contains
additional linker flags required