Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] trunk build failure on {Free,Net,Open}BSD
From: marco atzeri (marco.atzeri_at_[hidden])
Date: 2014-01-10 03:08:05


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