[glib] Honor the glib_cv_g_atomic_lock_free env var in configure



commit aa95853f9cd509b09a9c94a58df778ededad562f
Author: Enrique OcaÃa GonzÃlez <eocanha igalia com>
Date:   Tue Jan 24 13:24:51 2012 +0100

    Honor the glib_cv_g_atomic_lock_free env var in configure
    
    This fixes bug: https://bugzilla.gnome.org/show_bug.cgi?id=668572

 configure.ac |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/configure.ac b/configure.ac
index 03c6931..5289803 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2344,12 +2344,12 @@ dnl that then to silently fall back on emulated atomic ops just because
 dnl the user had the wrong build environment.
 
 dnl We may add other compilers here in the future...
-AC_MSG_CHECKING([for lock-free atomic intrinsics])
-AC_TRY_COMPILE([],
-               [__GCC_HAVE_SYNC_COMPARE_AND_SWAP_4;],
-               [glib_cv_g_atomic_lock_free=yes],
-               [glib_cv_g_atomic_lock_free=no])
-AC_MSG_RESULT($glib_cv_g_atomic_lock_free)
+
+AC_CACHE_CHECK([for lock-free atomic intrinsics], glib_cv_g_atomic_lock_free, [
+  AC_TRY_COMPILE([],
+                 [__GCC_HAVE_SYNC_COMPARE_AND_SWAP_4;],
+                 [glib_cv_g_atomic_lock_free=yes],
+                 [glib_cv_g_atomic_lock_free=no])])
 
 if test "$glib_cv_g_atomic_lock_free" = "no"; then
   SAVE_CFLAGS="${CFLAGS}"



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]