Paul Pluzhnikov bf27f0e2c7 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.		2018-05-04 10:08:09 -04:00
..
lib/gdb	…
py-all-events.def	…
py-arch.c	…
py-auto-load.c	…
py-block.c	…
py-bpevent.c	…
py-breakpoint.c	…
py-cmd.c	Change Python code to use new_reference	2018-04-30 11:33:12 -06:00
py-continueevent.c	…
py-event-types.def	…
py-event.c	…
py-event.h	…
py-events.h	…
py-evtregistry.c	…
py-evts.c	…
py-exitedevent.c	…
py-finishbreakpoint.c	…
py-frame.c	…
py-framefilter.c	Remove some uses of is_mi_like_p from py-framefilter.c	2018-04-30 12:59:04 -06:00
py-function.c	…
py-gdb-readline.c	…
py-inferior.c	…
py-infevents.c	…
py-infthread.c	…
py-instruction.c	…
py-instruction.h	…
py-lazy-string.c	…
py-linetable.c	…
py-newobjfileevent.c	…
py-objfile.c	…
py-param.c	Handle var_zuinteger and var_zuinteger_unlimited from Python	2018-05-02 10:31:55 -06:00
py-prettyprint.c	…
py-progspace.c	…
py-record-btrace.c	…
py-record-btrace.h	…
py-record-full.c	…
py-record-full.h	…
py-record.c	…
py-record.h	…
py-ref.h	…
py-signalevent.c	…
py-stopevent.c	…
py-stopevent.h	…
py-symbol.c	…
py-symtab.c	…
py-threadevent.c	…
py-type.c	Expose type alignment on gdb.Type	2018-04-30 11:25:31 -06:00
py-unwind.c	…
py-utils.c	…
py-value.c	…
py-varobj.c	…
py-xmethods.c	…
python-config.py	configure uses incorrect link order when testing libpython	2018-05-04 10:08:09 -04:00
python-internal.h	…
python.c	Handle var_zuinteger and var_zuinteger_unlimited from Python	2018-05-02 10:31:55 -06:00
python.h	…