Bug 1120444 - Use fdatasync properly instead of fsync where appropriate draft
authorLiang Wei <liangwei012@yeah.net>
Fri, 01 Sep 2017 09:03:22 +0200
changeset 657844 5a74030c4cacb7070656363b7a3a3366bad48ed5
parent 654693 5c627956860516c0144b41e7a9c9004024901742
child 729536 404e9f1b779a548b278e1a487bcd3049c038f48b
push id77639
push userbmo:liangwei012@yeah.net
push dateSat, 02 Sep 2017 02:31:05 +0000
bugs1120444
milestone57.0a1
Bug 1120444 - Use fdatasync properly instead of fsync where appropriate MozReview-Commit-ID: 4ObwOvWhrhx
old-configure.in
--- a/old-configure.in
+++ b/old-configure.in
@@ -3540,31 +3540,30 @@ dnl Check for sqlite
 dnl ========================================================
 
 MOZ_SYSTEM_SQLITE=
 MOZ_ARG_ENABLE_BOOL(system-sqlite,
 [  --enable-system-sqlite  Use system sqlite (located with pkgconfig)],
 MOZ_SYSTEM_SQLITE=1,
 MOZ_SYSTEM_SQLITE= )
 
+dnl ==============================
+dnl === SQLite fdatasync check ===
+dnl ==============================
+dnl Check to see if fdatasync is available
+AC_CHECK_FUNCS(fdatasync)
+
 if test -n "$MOZ_SYSTEM_SQLITE"
 then
     dnl ============================
     dnl === SQLite Version check ===
     dnl ============================
     dnl Check to see if the system SQLite package is new enough.
     PKG_CHECK_MODULES(SQLITE, sqlite3 >= $SQLITE_VERSION)
 
-    dnl ==============================
-    dnl === SQLite fdatasync check ===
-    dnl ==============================
-    dnl Check to see if fdatasync is available
-    AC_CHECK_FUNCS(fdatasync, HAVE_FDATASYNC=1, HAVE_FDATASYNC=)
-    
-
     dnl ==================================
     dnl === SQLITE_SECURE_DELETE check ===
     dnl ==================================
     dnl Check to see if the system SQLite package is compiled with
     dnl SQLITE_SECURE_DELETE enabled.
     AC_MSG_CHECKING(for SQLITE_SECURE_DELETE support in system SQLite)
     _SAVE_CFLAGS="$CFLAGS"
     CFLAGS="$CFLAGS $SQLITE_CFLAGS"