From: Dylan Baker <dylan@pnwbakers.com>
Date: Tue, 8 Oct 2019 20:38:01 +0000 (-0700)
Subject: meson/util: Don't run string_buffer tests on mingw
X-Git-Tag: upstream/19.3.0~1157
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1bf5e5a011a53cdb561eb2d66163c05aacba7a2c;p=platform%2Fupstream%2Fmesa.git

meson/util: Don't run string_buffer tests on mingw

They succeed with MSVC but not with MinGW. I don't understand why they
fail.

Acked-by: Kristian H. Kristensen <hoegsberg@google.com>
---

diff --git a/src/util/meson.build b/src/util/meson.build
index 096a3d9..f69ebe9 100644
--- a/src/util/meson.build
+++ b/src/util/meson.build
@@ -270,7 +270,10 @@ if with_tests
   subdir('tests/fast_idiv_by_const')
   subdir('tests/fast_urem_by_const')
   subdir('tests/hash_table')
-  subdir('tests/string_buffer')
+  if not (host_machine.system() == 'windows' and cc.get_id() == 'gcc')
+    # FIXME: These tests fail with mingw, but not with msvc.
+    subdir('tests/string_buffer')
+  endif
   if cc.has_header('sys/time.h')  # MinGW has this, but Vanilla windows doesn't
     subdir('tests/timespec')
   endif