_POSIX_SOURCE was a POSIX.1-1990 creation that was soon made
obsolete bu _POSIX_C_SOURCE. Retaining mention of it
in the feature test macro requirements section of the
SYNOPSIS doesn't contain important information, and may
mislead readers into actually trying to use this macro.
A few mentions of it a maintained in a some pages where
defining _POSIX_SOURCE inhibits some behavior.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Also remove redundant text covering FTM details that
are already provided in feature_test_macros(7).
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The right way to expose declarations for these Linux-specific
system calls was always _GNU_SOURCE. Mentioning the historical
use of _BSD_SOURCE and _SVID_SOURCE just clouds the issue.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Under the FTM requirements all of these pages document the
requirement for _ISOC99_SOURCE. And feature_test_macros(7) now
documents that "cc -std=c99" produces the same effect as defining
_ISOC99_SOURCE. So, all of these pages don't additionally need
to specify "or 'cc -std=c99'" under the FTM requirements
in the SYNOPSIS. Removing that redundant text also simplifies
the SYNOPSIS a little.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
_XOPEN_SOURCE_EXTENDED is obsolete (it existed in SUSv1, but not
subsequent standards). _XOPEN_SOURCE >= 500 produces the same
effects as (_XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED). Modifying
the SYNOPSIS of various ages that contain:
_XOPEN_SOURCE\ >=\ 500 ||
_XOPEN_SOURCE\ &&\ _XOPEN_SOURCE_EXTENDED
to just:
_XOPEN_SOURCE\ >=\ 500
This has the following benefits:
a) Simplifying the SYNOPSIS by removing ancient
historical information.
b) Preventing users from being misled into using
_XOPEN_SOURCE_EXTENDED in new source code.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
It seems that adjtimex() never needed _BSD_SOURCE (and my
earlier commit 5918743bc8 was simply a blunder.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Looking at <features.h> (or feature_test_macros(7)), one can
see that when _XOPEN_SOURCE is defined with the value 700
(or greater), then _POSIX_C_SOURCE is defined with the value
200809L (or greater). Therefore, terms in the man pages such as
_XOPEN_SOURCE\ >=\ 700 || _POSIX_C_SOURCE\ >=\ 200809L
can be simpified to:
_POSIX_C_SOURCE\ >=\ 200809L
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Looking at <features.h> (or feature_test_macros(7)), one can
see that when _XOPEN_SOURCE is defined with the value 600
(or greater), then _POSIX_C_SOURCE is defined with the value
200112L (or greater). Therefore, terms in the man pages such as
_XOPEN_SOURCE\ >=\ 600 || _POSIX_C_SOURCE\ >=\ 200112L
can be simplified to:
_POSIX_C_SOURCE\ >=\ 200112L
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>`
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Looking at <features.h> (or feature_test_macros(7)), one can
see that when _XOPEN_SOURCE is defined with the value 600
(or greater), then _POSIX_C_SOURCE is defined with the value
200112L (or greater). Therefore, terms in the man pages such as
_XOPEN_SOURCE\ >=\ 600 || _POSIX_C_SOURCE\ >=\ 200112L
can be simpified to:
_POSIX_C_SOURCE\ >=\ 200112L
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Update to use _DEFAULT_SOURCE, and also changes brought by
glibc commit 266865c0e7b79d4196e2cc393693463f03c90bd8.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The text has an incorrect description in NOTES, it says
that (2^32/HZ) - 300 is about 429 million. It is correct
only if HZ=10 which does not look common today. So just
removing "(i.e., about 429 million)" is good enough.
----
Signed-off-by: Naoya Kondo <kondo-naoya@jp.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This man page did not make it obvious which functions
should be used for manipulating signals sets, nor where
those functions were documented.
Reported-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk