From: Paul Eggert <eggert@cs.ucla.edu>
Date: Wed, 15 Jul 2020 17:32:14 +0000 (-0700)
Subject: Revert mistaken patch for Wine
X-Git-Tag: v2.69c~82
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6997ed9cee88f77e2c58969d55a85fbbfdf2a9d6;p=thirdparty%2Fautoconf.git

Revert mistaken patch for Wine

* lib/autoconf/lang.m4 (_AC_COMPILER_EXEEXT_CROSS):
Revert patch trying to cater to GNU/Linux builds
for Wine.  They should use --build as well as --host.
Problem reported by Bruno Haible in:
https://savannah.gnu.org/support/?110268
---

diff --git a/lib/autoconf/lang.m4 b/lib/autoconf/lang.m4
index e39c30b0..631e3cbc 100644
--- a/lib/autoconf/lang.m4
+++ b/lib/autoconf/lang.m4
@@ -595,21 +595,11 @@ ac_exeext=$ac_cv_exeext
 # detect cross-compiling on Blue Gene.  Note also that AC_COMPUTE_INT
 # requires programs that create files when not cross-compiling, so it
 # is safe and not a bad idea to check for this capability in general.
-#
-# Another false negative would occur on many modern linux distributions,
-# which would have Wine run automatically for Windows binaries. This is
-# a default configuration on several Debian-derivated distributions for
-# instance (see `update-binfmts`).
-# As a consequence the simple test program would run without errors,
-# even though we are on an obvious cross-compilation case and further
-# more complicated tests would fail.
 m4_define([_AC_COMPILER_EXEEXT_CROSS],
 [# Check that the compiler produces executables we can run.  If not, either
 # the compiler is broken, or we cross compile.
 AC_MSG_CHECKING([whether we are cross compiling])
-if test "$cross_compiling" = maybe && test "x$build" != "x$host"; then
-  cross_compiling=yes
-elif test "$cross_compiling" != yes; then
+if test "$cross_compiling" != yes; then
   _AC_DO_VAR(ac_link)
   if _AC_DO_TOKENS([./conftest$ac_cv_exeext]); then
     cross_compiling=no