From: Rhys Kidd <rhyskidd@gmail.com>
Date: Sun, 10 Sep 2017 15:40:21 +0000 (-0400)
Subject: Support all Apple clang/LLVM 5.1+
X-Git-Tag: VALGRIND_3_14_0~251
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=27e1503bc7bd767f3a98824176558beaa5a7c1d5;p=thirdparty%2Fvalgrind.git

Support all Apple clang/LLVM 5.1+

clang has been reasonably good at standards compliance for a while now, and
the Apple-shipped clang-variant in Xcode remains fairly close to upstream.

Let's assume that the Apple-shipped clang-variant is sufficient for
building valgrind, provided it is above a minimum version of 5.1.
---

diff --git a/configure.ac b/configure.ac
index f7e28a1b3c..2b4f958b35 100644
--- a/configure.ac
+++ b/configure.ac
@@ -154,7 +154,7 @@ AM_CONDITIONAL(COMPILER_IS_ICC, test $is_clang = icc)
 # Note: m4 arguments are quoted with [ and ] so square brackets in shell
 # statements have to be quoted.
 case "${is_clang}-${gcc_version}" in
-     applellvm-5.1|applellvm-6.*|applellvm-7.*|applellvm-8.*)
+     applellvm-5.1|applellvm-[[6-9]].*|applellvm-[[1-9][0-9]]*)
 	AC_MSG_RESULT([ok (Apple LLVM version ${gcc_version})])
 	;;
      icc-1[[3-9]].*)
@@ -168,7 +168,7 @@ case "${is_clang}-${gcc_version}" in
 	;;
      *)
 	AC_MSG_RESULT([no (${is_clang}-${gcc_version})])
-	AC_MSG_ERROR([please use gcc >= 3.0 or clang >= 2.9 or icc >= 13.0])
+	AC_MSG_ERROR([please use gcc >= 3.0 or clang >= 2.9 or icc >= 13.0 or Apple LLVM >= 5.1])
 	;;
 esac