From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stijn Hinterding
<contact-Tcs81MCHamfqOYT2WTFYB/P6llvjuJOh@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug in process_vm_readv manpage: no mention of need to define _GNU_SOURCE
Date: Mon, 05 May 2014 20:06:30 +0200 [thread overview]
Message-ID: <5367D326.3040101@gmail.com> (raw)
In-Reply-To: <32aae98b8af2ee4af07f79be33514569-Tcs81MCHamfqOYT2WTFYB/P6llvjuJOh@public.gmane.org>
On 05/05/2014 07:55 PM, Stijn Hinterding wrote:
> Dear sirs,
>
> Following is a bug report for the process_vm_writev / process_vm_readv manpage.
>
> Platform: Ubuntu 13.10 x86_64
> Man-pages release: 3.54
> Kernel version: 3.11.0-20-generic
> glibc version: 2.17
>
>
> Description:
> GNU extensions need te be enabled when using these functions (ie, define _GNU_SOURCE).
> This is not mentioned in the manpage, thus users will encounter errors upon compiling.
>
> Suggestion:
> Mention that _GNU_SOURCE needs to be declared before including <sys/uio.h>
Done. Thanks for the report, Stijn.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
parent reply other threads:[~2014-05-05 18:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <32aae98b8af2ee4af07f79be33514569-Tcs81MCHamfqOYT2WTFYB/P6llvjuJOh@public.gmane.org>]
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=5367D326.3040101@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=contact-Tcs81MCHamfqOYT2WTFYB/P6llvjuJOh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.