From cc1bfb5addeb6e1a580ebaeed2c5d89463771226 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 23 Aug 2006 23:40:21 +0000 Subject: [PATCH] * m4/fsusage.m4 (gl_FILE_SYSTEM_USAGE): Don't consider BeOS statvfs as unusable. --- m4/ChangeLog | 3 +++ m4/fsusage.m4 | 6 ++++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/m4/ChangeLog b/m4/ChangeLog index 21de085e4..7957ca3ad 100644 --- a/m4/ChangeLog +++ b/m4/ChangeLog @@ -1,5 +1,8 @@ 2006-08-23 Bruno Haible + * fsusage.m4 (gl_FILE_SYSTEM_USAGE): Don't consider BeOS statvfs + as unusable. + * lock.m4 (gl_LOCK_EARLY): Renamed from gl_LOCK. (gl_LOCK_BODY): Remove gl_PREREQ_LOCK invocation. (gl_LOCK): New macro. diff --git a/m4/fsusage.m4 b/m4/fsusage.m4 index 78266f110..23116b5f2 100644 --- a/m4/fsusage.m4 +++ b/m4/fsusage.m4 @@ -1,4 +1,4 @@ -#serial 18 +#serial 19 # Obtaining file system usage information. # Copyright (C) 1997, 1998, 2000, 2001, 2003, 2004, 2005, 2006 Free Software @@ -48,10 +48,12 @@ if test $ac_fsusage_space = no; then # SVR4 AC_CACHE_CHECK([for statvfs function (SVR4)], fu_cv_sys_stat_statvfs, [AC_TRY_LINK([#include -#ifdef __GLIBC__ +#if defined __GLIBC__ && !defined __BEOS__ Do not use statvfs on systems with GNU libc, because that function stats all preceding entries in /proc/mounts, and that makes df hang if even one of the corresponding file systems is hard-mounted, but not available. +statvfs in GNU libc on BeOS operates differently: it only makes a system +call. #endif #include ], [struct statvfs fsd; statvfs (0, &fsd);], -- 2.11.0