From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Markus Peuhkuri <puhuri-X3B1VOXEql0@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: memrchr(3): depends on _GNU_SOURCE
Date: Sat, 5 Dec 2009 06:06:38 +0100 [thread overview]
Message-ID: <cfd18e0f0912042106we0323fcx56556b438bca5591@mail.gmail.com> (raw)
In-Reply-To: <4B0D3255.9080305-X3B1VOXEql0@public.gmane.org>
Hello Markus,
On Wed, Nov 25, 2009 at 2:34 PM, Markus Peuhkuri <puhuri-X3B1VOXEql0@public.gmane.org> wrote:
> At manual page (memchr, memrchr and rawmemchr) it is listed that only
> rawmemchr needs _GNU_SOURCE feature test macro. However, at least in
> /usr/include/string.h shipped with Debian Lenny and Ubuntu 9.04 both
> have also memrchr in same #ifdef __USE_GNU block.
>
> Correction:
>
> --- memchr.old 2008-07-26 15:31:57.431082210 +0200
> +++ memchr.3 2009-11-25 15:31:39.000000000 +0200
> @@ -46,6 +46,8 @@
> .BR feature_test_macros (7)):
> .in
> .sp
> +.BR memrchr ():
> +_GNU_SOURCE
> .BR rawmemchr ():
> _GNU_SOURCE
> .SH DESCRIPTION
>
>
> (or should them be at same line.)
Thanks for the report. Indeed, it should be at the same line. Fixed for 3.24.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
--
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
prev parent reply other threads:[~2009-12-05 5:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 13:34 memrchr(3): depends on _GNU_SOURCE Markus Peuhkuri
[not found] ` <4B0D3255.9080305-X3B1VOXEql0@public.gmane.org>
2009-12-05 5:06 ` Michael Kerrisk [this message]
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=cfd18e0f0912042106we0323fcx56556b438bca5591@mail.gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=puhuri-X3B1VOXEql0@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).