Bug#290880: (In reply to comment #4) > However the current behavior violates the ISO C standard (or the system > documentation is incorrect). Which part of the standard do you believe this violates? SUSv3 permits the Linux behaviour, as far as I can see. And I believe it is common on other implementations also. > But the solution to reserve the fd 0, 1 and 2 for stdin, stdout and stderr in > ISO C programs (as long as a race condition doesn't occur) would be OK. Note > that a C implementation isn't required to have fully reentrant standard > functions, so that if the programmer wants stdin, stdout and stderr to really > correspond to the standard streams, then he should also make sure that no race > condition occurs. I do not believe any change should be made. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295859 for further information. Cheers, Re: #290880 strerror_r only available with __USE_XOPEN2K defined

[Michael Kerrisk]

Gunaydin Baurjan, Hi Joey,

I have added

#define _XOPEN_SOURCE 600

for the prototype of this function:

       #include <string.h>

       char *strerror(int errnum);

       #define _XOPEN_SOURCE 600
       #include <string.h>

       int strerror_r(int errnum, char *buf, size_t n);

The fix will appear in man-pages 2.04.

Cheers,

Michael

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 

Want to help with man page maintenance?  Grab the latest
tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/
and grep the source files for 'FIXME'.

Please submit non-trivial man page suggestions as 
"diff -u" patches.

Geschenkt: 3 Monate GMX ProMail gratis + 3 Ausgaben stern gratis
++ Jetzt anmelden & testen ++ http://www.gmx.net/de/go/promail ++


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]