Il 1/10/2014 5:00 AM, Paul Hargrove ha scritto:
The following might be helpful:
http://stackoverflow.com/questions/1653163/difference-between-statvfs-and-statfs-system-calls
It seems to indicate that even if one does find a statfs() function,
there are multiple os-dependent versions and it should therefore be
avoided. Since statvfs() is defined by POSIX, it should be preferred.
If I am not mistaken, reordering the #if logic in path.c to use *only*
statvfs() when it is available (and *not* trying both as is done now)
would resolve the problems I am seeing with NetBSD and Solaris WITHOUT
any need to change the configure logic. However, if one does want to
keep the current logic (or at least something similar) it looks like
configure should not assume statfs() is available without *also*
confirming that "struct statfs" is available.
-Paul
statvfs() is available on CYGWIN,
http://cygwin.com/cygwin-api/compatibility.html#std-susv4
so no issue to use it as default for me
Thanks
Marco
