From: Andrew Clayton <andrew-gyMb1R/nBgN3uBD2Ct+Y/qxOck334EZe@public.gmane.org>
To: andrew-gyMb1R/nBgN3uBD2Ct+Y/qxOck334EZe@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] getgroups.2: FTM requirements fix for setgroups(2)
Date: Sat, 12 Nov 2016 14:07:12 +0000 [thread overview]
Message-ID: <1478959632-47079-1-git-send-email-andrew@digital-domain.net> (raw)
This fix's commit 51c612f (... Update FTM requirements
(_DEFAULT_SOURCE))
This commit updated numerous pages for the _SVID_SOURCE & _BSD_SOURCE
deprecations and the new use of _DEFAULT_SOURCE.
However during this conversion for setgroups(2) _BSD_SOURCE got replaced
by _SVID_SOURCE under the 'Glibc 2.19 and earlier:' heading.
Put it back to _BSD_SOURCE. This was confirmed by building under a Glibc
2.17 system and using _SVID_SOURCE resulted in a
warning: implicit declaration of function ‘setgroups’ [-Wimplicit-function-declaration]
message. Using _BSD_SOURCE gives a clean compile.
Signed-off-by: Andrew Clayton <andrew-gyMb1R/nBgN3uBD2Ct+Y/qxOck334EZe@public.gmane.org>
---
man2/getgroups.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/getgroups.2 b/man2/getgroups.2
index bd9d7f4..16e9864 100644
--- a/man2/getgroups.2
+++ b/man2/getgroups.2
@@ -52,7 +52,7 @@ Feature Test Macro Requirements for glibc (see
Since glibc 2.19:
_DEFAULT_SOURCE
Glibc 2.19 and earlier:
- _SVID_SOURCE
+ _BSD_SOURCE
.SH DESCRIPTION
.PP
.BR getgroups ()
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2016-11-12 14:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1478959632-47079-1-git-send-email-andrew@digital-domain.net \
--to=andrew-gymb1r/nbgn3ubd2ct+y/qxock334eze@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).