Joel Brobecker added the comment:
More update on this patch: It's incomplete, and possibly wrong, unfortunately.
The issue that someone else noticed is that it does not handle the case when
Python was configured with --libdir=...; and I think that the default lib dir
on platforms su
Joel Brobecker added the comment:
I agree that more testing in head would be useful before possibly considering
inclusion in one of the bug-fix releases. Given that this only affects binaries
installed at a different location than the configure prefix, this seems hardly
critical (and easy to
Joel Brobecker added the comment:
GDB can suffer from the same sort of problem. In my case, I picked up a Python
binary tarball built on a different machine (without --enable-shared), and the
path in -L returned by python-config --ldflags refered to the prefix used
at configure time. But
