public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] configure uses incorrect link order when testing libpython
Date: Fri, 04 May 2018 14:14:00 -0000 [thread overview]
Message-ID: <bf27f0e2c76839af8524e053cca271934150a90c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT bf27f0e2c76839af8524e053cca271934150a90c ***
Author: Paul Pluzhnikov <ppluzhnikov@google.com>
Branch: master
Commit: bf27f0e2c76839af8524e053cca271934150a90c
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.
next reply other threads:[~2018-05-04 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 14:14 sergiodj+buildbot [this message]
2018-05-04 14:30 ` *** COMPILATION FAILED *** Failures on Fedora-i686, branch master *** BREAKAGE *** sergiodj+buildbot
2018-05-04 14:32 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot
2018-05-04 14:34 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-05-04 14:37 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-05-04 14:39 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-05-04 14:43 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-05-04 14:46 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-05-04 14:48 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-05-04 14:58 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-05-04 15:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-05-04 17:21 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-05-04 18:20 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf27f0e2c76839af8524e053cca271934150a90c@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).