From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57965) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QQjQL-0002kl-CK for qemu-devel@nongnu.org; Sun, 29 May 2011 13:05:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QQjQK-0003nZ-AL for qemu-devel@nongnu.org; Sun, 29 May 2011 13:05:09 -0400 Message-Id: <8736D7AA-0AED-41E6-8A48-24BB1A948A8C@web.de> From: =?ISO-8859-1?Q?Andreas_F=E4rber?= In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 29 May 2011 19:05:04 +0200 References: <1306516951-31105-1-git-send-email-cerbere@gmail.com> <1306516951-31105-2-git-send-email-cerbere@gmail.com> Sender: andreas.faerber@web.de Subject: Re: [Qemu-devel] [PATCH 1/6] Fix incorrect check for fdatasync() in configure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexandre Raymond Cc: qemu-trivial@nongnu.org, Stefan Hajnoczi , QEMU Developers 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<---- > The following symbolic constants, if defined in , shall have > a value of -1, 0, or greater, unless otherwise specified below. If > these are undefined, the fpathconf(), pathconf(), or sysconf() > functions can be used to determine whether the option is provided for > a particular invocation of the application. > > If a symbolic constant is defined with the value -1, the option is not > supported. Headers, data types, and function interfaces required only > for the option need not be supplied. An application that attempts to > use anything associated only with the option is considered to be > requiring an extension. > > If a symbolic constant is defined with a value greater than zero, the > option shall always be supported when the application is executed. All > headers, data types, and functions shall be present and shall operate > as specified. > > If a symbolic constant is defined with the value zero, all headers, > data types, and functions shall be present. The application can check > at runtime to see whether the option is supported by calling > fpathconf(), pathconf(), or sysconf() with the indicated name > parameter. > ----8<---- Indeed, confirmed in Issue 7, thanks a lot. Could you please provide me with an updated commit message saying so? Then I'll apply it. Andreas