public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove python_has_threads check in configure.ac
Date: Thu, 24 Oct 2019 20:00:00 -0000	[thread overview]
Message-ID: <cbb5a2ea493d0cbe49defc3d45ebe3b7e2728a51@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT cbb5a2ea493d0cbe49defc3d45ebe3b7e2728a51 ***

commit cbb5a2ea493d0cbe49defc3d45ebe3b7e2728a51
Author:     Christian Biesinger <cbiesinger@google.com>
AuthorDate: Thu Oct 24 13:51:55 2019 -0500
Commit:     Christian Biesinger <cbiesinger@google.com>
CommitDate: Thu Oct 24 14:14:07 2019 -0500

    Remove python_has_threads check in configure.ac
    
    The only use of python_has_threads has been removed in
    commit 404f29021abaef86a341663444fb069eb1f0282a
    
    gdb/ChangeLog:
    
    2019-10-24  Christian Biesinger  <cbiesinger@google.com>
    
            * configure: Rebuild.
            * configure.ac: Remove code that sets python_has_threads.
    
    Change-Id: I75f1b873562bc2abc6f2db17699a3e82fcfd2de3

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 0545f4a57b..664000add4 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2019-10-24  Christian Biesinger  <cbiesinger@google.com>
+
+	* configure: Regenerate.
+	* configure.ac: Remove code that sets python_has_threads.
+
 2019-10-24  Christian Biesinger  <cbiesinger@google.com>
 
 	* config.in: Regenerate.
diff --git a/gdb/configure b/gdb/configure
index dcd614118a..4e2247d7ca 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -10664,34 +10664,6 @@ $as_echo "${PYTHON_CFLAGS}" >&6; }
            fi
            ;;
   esac
-
-  # Note that "python -m threading" cannot be used to check for
-  # threading support due to a bug in Python 2.7.3
-  # (http://bugs.python.org/issue15567).
-  { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether python supports threads" >&5
-$as_echo_n "checking whether python supports threads... " >&6; }
-  saved_CPPFLAGS="${CPPFLAGS}"
-  CPPFLAGS="${PYTHON_CPPFLAGS}"
-  # Note that the test is reversed so that python_has_threads=yes on
-  # unexpected failures.
-  cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h.  */
-
-#include <Python.h>
-#ifdef WITH_THREAD
-# error
-#endif
-
-_ACEOF
-if ac_fn_c_try_cpp "$LINENO"; then :
-  python_has_threads=no
-else
-  python_has_threads=yes
-fi
-rm -f conftest.err conftest.i conftest.$ac_ext
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: ${python_has_threads}" >&5
-$as_echo "${python_has_threads}" >&6; }
-  CPPFLAGS="${saved_CPPFLAGS}"
 else
   # Even if Python support is not compiled in, we need to have this file
   # included so that the "python" command, et.al., still exists.
diff --git a/gdb/configure.ac b/gdb/configure.ac
index f11dccd7fa..cb331be7ae 100644
--- a/gdb/configure.ac
+++ b/gdb/configure.ac
@@ -948,23 +948,6 @@ if test "${have_libpython}" != no; then
            fi
            ;;
   esac
-
-  # Note that "python -m threading" cannot be used to check for
-  # threading support due to a bug in Python 2.7.3
-  # (http://bugs.python.org/issue15567).
-  AC_MSG_CHECKING(whether python supports threads)
-  saved_CPPFLAGS="${CPPFLAGS}"
-  CPPFLAGS="${PYTHON_CPPFLAGS}"
-  # Note that the test is reversed so that python_has_threads=yes on
-  # unexpected failures.
-  AC_PREPROC_IFELSE([AC_LANG_SOURCE([[
-#include <Python.h>
-#ifdef WITH_THREAD
-# error
-#endif
-  ]])], [python_has_threads=no], [python_has_threads=yes])
-  AC_MSG_RESULT(${python_has_threads})
-  CPPFLAGS="${saved_CPPFLAGS}"
 else
   # Even if Python support is not compiled in, we need to have this file
   # included so that the "python" command, et.al., still exists.


             reply	other threads:[~2019-10-24 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 20:00 gdb-buildbot [this message]
2019-10-24 20:00 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot
2019-10-24 20:13 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-11-12 11:47 ` Failures on Fedora-i686, " gdb-buildbot
2019-11-12 11:58 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-11-12 12:43 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2019-11-12 13:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-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=cbb5a2ea493d0cbe49defc3d45ebe3b7e2728a51@gdb-build \
    --to=gdb-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).