Mesa (7.11): Don' t use $CLANG since it will collide with the static analyzer.

Jeremy Huddleston jeremyhu at
Fri Jan 27 09:05:33 PST 2012

Module: Mesa
Branch: 7.11
Commit: 906f670f1a1f33d69139f520ee931b268049eac6

Author: Jeremy Huddleston <jeremyhu at>
Date:   Thu May  5 14:08:57 2011 -0700 Don't use $CLANG since it will collide with the static analyzer.

We just prefix the $CLANG environment variable in with acv_mesa_

Found by: tinderbox
Signed-off-by: Jeremy Huddleston <jeremyhu at>
Reviewed-by: Ian Romanick <ian.d.romanick at>
(cherry picked from commit b728eefb06c26e4b5a25db31bbda9fcf4d015e17)

--- |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/ b/
index 817bf8b..fb74cfd 100644
--- a/
+++ b/
@@ -75,13 +75,13 @@ AC_COMPILE_IFELSE(
        not clang
-[CLANG=yes], [CLANG=no])
+[acv_mesa_CLANG=yes], [acv_mesa_CLANG=no])
 dnl If we're using GCC, make sure that it is at least version 3.3.0.  Older
 dnl versions are explictly not supported.
-if test "x$GCC" = xyes -a "x$CLANG" = xno; then
+if test "x$GCC" = xyes -a "x$acv_mesa_CLANG" = xno; then
     AC_MSG_CHECKING([whether gcc version is sufficient])

More information about the mesa-commit mailing list