Processing commands for [EMAIL PROTECTED]:
tag 119974 + pending
Bug#119974: libc6-dev: fsync() doesn't get declared on unistd.h without
__USE_BSD or __USE_XOPEN
Tags were: pending
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
tag 119974 + pending
thanks
I checked in the POSIX doc, FWIW here is what I found:
fsync was first introduced it seems as an XOPEN extension. Hence the
__USE_XOPEN guard, and defining _XOPEN_SOURCE indeed works.
Else, wrt POSIX, fsync last updates are in posix 1003.1-2001.
Just saying
tag 119974 + pending
thanks
I checked in the POSIX doc, FWIW here is what I found:
fsync was first introduced it seems as an XOPEN extension. Hence the
__USE_XOPEN guard, and defining _XOPEN_SOURCE indeed works.
Else, wrt POSIX, fsync last updates are in posix 1003.1-2001.
Just saying
Processing commands for [EMAIL PROTECTED]:
tag 119974 + pending
Bug#119974: libc6-dev: fsync() doesn't get declared on unistd.h without
__USE_BSD or __USE_XOPEN
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
On Mon, Jan 13, 2003 at 08:02:14AM -0500, H. S. Teoh wrote:
So you're saying that even if you ask for POSIX.1b, you still don't get
fsync()?
Yes. Try this:
$ cat test.c
#include unistd.h
void foo (void) { fsync(0); }
$ gcc -Wall -D_POSIX_C_SOURCE=199309L -c test.c
test.c: In function `foo':
Hi, I've just tested this bug, and observed something rather interesting:
% cpp /usr/include/unistd.h |grep fsync
extern int fsync (int __fd) ;
% cpp -D_POSIX_SOURCE /usr/include/unistd.h | grep fsync
%
So it gets included in the default header file, but not when _POSIX_SOURCE
is defined. Now
On Sat, Dec 28, 2002 at 12:07:14PM -0500, H. S. Teoh wrote:
Hi, I've just tested this bug, and observed something rather interesting:
% cpp /usr/include/unistd.h |grep fsync
extern int fsync (int __fd) ;
% cpp -D_POSIX_SOURCE /usr/include/unistd.h | grep fsync
%
So it gets included in
On Sat, Dec 28, 2002 at 07:23:06PM -0500, Daniel Jacobowitz wrote:
[snip]
It's guarded by:
#if defined __USE_BSD || defined __USE_XOPEN
_POSIX_SOURCE is:
_POSIX_SOURCEIEEE Std 1003.1.
i.e. not 1b.
Ahh, that explains it.
On the other hand, given:
_POSIX_C_SOURCE If
On Sat, Dec 28, 2002 at 08:03:40PM -0500, H. S. Teoh wrote:
On Sat, Dec 28, 2002 at 07:23:06PM -0500, Daniel Jacobowitz wrote:
[snip]
It's guarded by:
#if defined __USE_BSD || defined __USE_XOPEN
_POSIX_SOURCE is:
_POSIX_SOURCEIEEE Std 1003.1.
i.e. not 1b.
Ahh, that
Hi, I've just tested this bug, and observed something rather interesting:
% cpp /usr/include/unistd.h |grep fsync
extern int fsync (int __fd) ;
% cpp -D_POSIX_SOURCE /usr/include/unistd.h | grep fsync
%
So it gets included in the default header file, but not when _POSIX_SOURCE
is defined. Now
On Sat, Dec 28, 2002 at 12:07:14PM -0500, H. S. Teoh wrote:
Hi, I've just tested this bug, and observed something rather interesting:
% cpp /usr/include/unistd.h |grep fsync
extern int fsync (int __fd) ;
% cpp -D_POSIX_SOURCE /usr/include/unistd.h | grep fsync
%
So it gets included in
On Sat, Dec 28, 2002 at 07:23:06PM -0500, Daniel Jacobowitz wrote:
[snip]
It's guarded by:
#if defined __USE_BSD || defined __USE_XOPEN
_POSIX_SOURCE is:
_POSIX_SOURCEIEEE Std 1003.1.
i.e. not 1b.
Ahh, that explains it.
On the other hand, given:
_POSIX_C_SOURCE If
On Sat, Dec 28, 2002 at 08:03:40PM -0500, H. S. Teoh wrote:
On Sat, Dec 28, 2002 at 07:23:06PM -0500, Daniel Jacobowitz wrote:
[snip]
It's guarded by:
#if defined __USE_BSD || defined __USE_XOPEN
_POSIX_SOURCE is:
_POSIX_SOURCEIEEE Std 1003.1.
i.e. not 1b.
Ahh, that
13 matches
Mail list logo
