From 0816953be5f1f5f46f6bf45fee44d25f75e2a291 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Diego=20=27Flameeyes=27=20Petten=C3=B2?=
 <flameeyes@gmail.com>
Date: Thu, 22 May 2008 23:40:39 +0200
Subject: Don't leak -Werror into the build system.

Using the same variable name to save and restore CFLAGS between macros
is a bad idea.
---
 m4/attributes.m4 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'm4')

diff --git a/m4/attributes.m4 b/m4/attributes.m4
index 2b7175b1c..ed15b6670 100644
--- a/m4/attributes.m4
+++ b/m4/attributes.m4
@@ -190,12 +190,12 @@ AC_DEFUN([CC_FLAG_VISIBILITY], [
   AC_REQUIRE([CC_CHECK_WERROR])
   AC_CACHE_CHECK([if $CC supports -fvisibility=hidden],
     [cc_cv_flag_visibility],
-    [ac_save_CFLAGS="$CFLAGS"
+    [cc_flag_visibility_save_CFLAGS="$CFLAGS"
      CFLAGS="$CFLAGS $cc_cv_werror"
      CC_CHECK_CFLAGS_SILENT([-fvisibility=hidden],
 	cc_cv_flag_visibility='yes',
 	cc_cv_flag_visibility='no')
-     CFLAGS="$ac_save_CFLAGS"])
+     CFLAGS="$cc_flag_visibility_save_CFLAGS"])
   
   if test "x$cc_cv_flag_visibility" = "xyes"; then
     AC_DEFINE([SUPPORT_FLAG_VISIBILITY], 1, [Define this if the compiler supports the -fvisibility flag])
-- 
cgit v1.2.3