Build with -DMS_WIN64 on amd64-windows if Python enabled...

... and building with GCC.

gdb/ChangeLog:

        * configure.ac: Build with -DMS_WIN64 if building with Python
        enabled using GCC on amd64-windows.
        * configure: Regenerate.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 5f5eaf97ba57e150c17a60dc88803a705b2c21b8..902667b6a928b09680b718091938b05d138f1249 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2012-10-15  Joel Brobecker  <brobecker@adacore.com>
+
+       * configure.ac: Build with -DMS_WIN64 if building with Python
+       enabled using GCC on amd64-windows.
+       * configure: Regenerate.
+
 2012-10-15  Tom Tromey  <tromey@redhat.com>
 
        PR python/14635:

diff --git a/gdb/configure b/gdb/configure
index d913de6e7ef69775d1631a42002ebf753a634481..6941e9c056049f116f426557c9ab4a8c0104cd71 100755 (executable)
--- a/gdb/configure
+++ b/gdb/configure
@@ -8472,11 +8472,25 @@ $as_echo "${PYTHON_CFLAGS}" >&6; }
   # unilaterally defined, and that in turn causes _SGIAPI to evaluate
   # to false.  So, we work around this issue by defining siginfo ourself
   # though the command-line.
+  #
+  # On x64 Windows, Python's include headers, and pyconfig.h in
+  # particular, rely on MS_WIN64 macro to detect that it's a 64bit
+  # version of Windows.  Unfortunately, MS_WIN64 is only defined if
+  # _MSC_VER, a Microsoft-specific macro, is defined.  So, when
+  # building on x64 Windows with GCC, we define MS_WIN64 ourselves.
+  # The issue was reported to the Python community, but still isn't
+  # solved as of 2012-10-02 (http://bugs.python.org/issue4709).
+
   case "$gdb_host" in
     irix*) if test "${GCC}" = yes; then
              CPPFLAGS="$CPPFLAGS -Dsiginfo=__siginfo"
            fi
            ;;
+    mingw64)
+           if test "${GCC}" = yes; then
+             CPPFLAGS="$CPPFLAGS -DMS_WIN64"
+           fi
+           ;;
   esac
 
   # Note that "python -m threading" cannot be used to check for

diff --git a/gdb/configure.ac b/gdb/configure.ac
index c0fd0e13b8d81ae2a455c8bffaf983cfd8287a34..fc181fd5e369c334b4d4782ce256dbbf0b7328b1 100644 (file)
--- a/gdb/configure.ac
+++ b/gdb/configure.ac
@@ -989,11 +989,25 @@ if test "${have_libpython}" != no; then
   # unilaterally defined, and that in turn causes _SGIAPI to evaluate
   # to false.  So, we work around this issue by defining siginfo ourself
   # though the command-line.
+  #
+  # On x64 Windows, Python's include headers, and pyconfig.h in
+  # particular, rely on MS_WIN64 macro to detect that it's a 64bit
+  # version of Windows.  Unfortunately, MS_WIN64 is only defined if
+  # _MSC_VER, a Microsoft-specific macro, is defined.  So, when
+  # building on x64 Windows with GCC, we define MS_WIN64 ourselves.
+  # The issue was reported to the Python community, but still isn't
+  # solved as of 2012-10-02 (http://bugs.python.org/issue4709).
+
   case "$gdb_host" in
     irix*) if test "${GCC}" = yes; then
              CPPFLAGS="$CPPFLAGS -Dsiginfo=__siginfo"
            fi
            ;;
+    mingw64)
+           if test "${GCC}" = yes; then
+             CPPFLAGS="$CPPFLAGS -DMS_WIN64"
+           fi
+           ;;
   esac
 
   # Note that "python -m threading" cannot be used to check for