Re: [Qemu-devel] [PATCH 1/6] Fix incorrect check for fdatasync() in configure

2011-05-29 Thread Andreas Färber
Hi Alexandre, Am 29.05.2011 um 17:46 schrieb Alexandre Raymond: According to this excerpt from The Open Group Base Specifications Issue 6 (http://pubs.opengroup.org/onlinepubs/009695399/basedefs/unistd.h.html ), '>0' indeed means that the functionality is implemented and can be used. 8<--

Re: [Qemu-devel] [PATCH 1/6] Fix incorrect check for fdatasync() in configure

2011-05-29 Thread Alexandre Raymond
Hi Andreas, According to this excerpt from The Open Group Base Specifications Issue 6 (http://pubs.opengroup.org/onlinepubs/009695399/basedefs/unistd.h.html), '>0' indeed means that the functionality is implemented and can be used. 8< The following symbolic constants, if defined in , shall

Re: [Qemu-devel] [PATCH 1/6] Fix incorrect check for fdatasync() in configure

2011-05-29 Thread Andreas Färber
Am 27.05.2011 um 19:22 schrieb Alexandre Raymond: For some reason, darwin provides a symbol for fdatasync(), but doesn't officially support it. The manpage for fdatasync on Linux states the following: "On POSIX systems on which fdatasync() is available, _POSIX_SYNCHRONIZED_IO is defined in

[Qemu-devel] [PATCH 1/6] Fix incorrect check for fdatasync() in configure

2011-05-27 Thread Alexandre Raymond
For some reason, darwin provides a symbol for fdatasync(), but doesn't officially support it. The manpage for fdatasync on Linux states the following: "On POSIX systems on which fdatasync() is available, _POSIX_SYNCHRONIZED_IO is defined in to a value greater than 0." In fact, unistd.h defin