configure uses incorrect link order when testing libpython
authorPaul Pluzhnikov <ppluzhnikov@google.com>
Fri, 4 May 2018 14:07:58 +0000 (10:07 -0400)
committerSimon Marchi <simon.marchi@ericsson.com>
Fri, 4 May 2018 14:08:09 +0000 (10:08 -0400)
commitbf27f0e2c76839af8524e053cca271934150a90c
treefae5cc97580cdf5b61489be7610f0124187c342e
parent089a949083dcd5c679376033e975d54093007408
configure uses incorrect link order when testing libpython

References:

https://stackoverflow.com/a/49868387
https://sourceware.org/bugzilla/show_bug.cgi?id=11420

Configure uses "gcc -o conftest -g ... conftest.c -ldl -lncurses -lm -ldl
... -lpthread ... -lpython2.7" when deciding whether give libpython is
usable.

That of course is the wrong link order, and only works for shared libraries
(mostly by accident), and only on some systems.

gdb/ChangeLog:

PR gdb/11420
* configure.ac: Prepend libpython.
* python/python-config.py: Likewise.
* configure: Regenerate.
gdb/ChangeLog
gdb/configure
gdb/configure.ac
gdb/python/python-config.py