Bug 1120444 - Use fdatasync properly instead of fsync where appropriate draft
authorLiang Wei <liangwei012@yeah.net>
Tue, 29 Aug 2017 06:35:26 +0200
changeset 654693 5c627956860516c0144b41e7a9c9004024901742
parent 653709 f819969d7619f01e806e2685b8b3196f64624551
child 657198 edf6bee66bbdeee2f49a2e8a637935108036ae4b
child 657844 5a74030c4cacb7070656363b7a3a3366bad48ed5
push id76649
push userbmo:liangwei012@yeah.net
push dateTue, 29 Aug 2017 05:18:20 +0000
bugs1120444
milestone57.0a1
Bug 1120444 - Use fdatasync properly instead of fsync where appropriate MozReview-Commit-ID: 7MRA67AHEJA
old-configure.in
--- a/old-configure.in
+++ b/old-configure.in
@@ -3548,16 +3548,23 @@ MOZ_SYSTEM_SQLITE= )
 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"