aboutsummaryrefslogtreecommitdiff
path: root/manual/conf.texi
diff options
context:
space:
mode:
authorJoseph Myers <joseph@codesourcery.com>2012-02-18 18:21:52 +0000
committerJoseph Myers <joseph@codesourcery.com>2012-02-18 18:21:52 +0000
commit366842e73e7fc4e29dd0d6571a6e046b6e329ed1 (patch)
treeeb8f38634a4a1eed177ba18cbf43aec29d7b95a2 /manual/conf.texi
parentdd54084dd9549ae15c12db248571ad76946b8712 (diff)
downloadglibc-366842e73e7fc4e29dd0d6571a6e046b6e329ed1.zip
glibc-366842e73e7fc4e29dd0d6571a6e046b6e329ed1.tar.gz
glibc-366842e73e7fc4e29dd0d6571a6e046b6e329ed1.tar.bz2
Do not claim that GCC predefines __POSIX__.
Diffstat (limited to 'manual/conf.texi')
-rw-r--r--manual/conf.texi5
1 files changed, 0 insertions, 5 deletions
diff --git a/manual/conf.texi b/manual/conf.texi
index 605e305..30499d9 100644
--- a/manual/conf.texi
+++ b/manual/conf.texi
@@ -248,11 +248,6 @@ by including @file{unistd.h} and then checking whether
probably fail because there is no @file{unistd.h}. We do not know of
@emph{any} way you can reliably test at compilation time whether your
target system supports POSIX or whether @file{unistd.h} exists.
-
-The GNU C compiler predefines the symbol @code{__POSIX__} if the target
-system is a POSIX system. Provided you do not use any other compilers
-on POSIX systems, testing @code{defined (__POSIX__)} will reliably
-detect such systems.
@end deftypevr
@comment unistd.h