public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15312] SEEK_HOLE and SEEK_DATA not exported as expected
Date: Wed, 27 Mar 2013 20:51:00 -0000	[thread overview]
Message-ID: <bug-15312-131-bBGS1QWBtf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15312-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15312

--- Comment #5 from Michael Kerrisk <mtk.manpages at gmail dot com> 2013-03-27 20:50:59 UTC ---
(In reply to comment #3)
> No, I want the man pages clear enough that you know to add a define for

Thanks, Andreas, for adding me. I've added this text to the lseek(2) page:

       The _GNU_SOURCE feature test macro must be defined in order  to
       obtain   the   definitions  of  SEEK_DATA  and  SEEK_HOLE  from
       <unistd.h>.

> have a look at /usr/include/unistd.h and read the glibc info pages about
> feature test macros to learn about _GNU_SOURCE.

Or, for even more detail:

http://man7.org/linux/man-pages/man7/feature_test_macros.7.html

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-03-27 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 14:28 [Bug libc/15312] New: " sourceware.org@jan-o-sch.net
2013-03-27 14:50 ` [Bug libc/15312] " aj at suse dot de
2013-03-27 15:05 ` sourceware.org@jan-o-sch.net
2013-03-27 15:12 ` aj at suse dot de
2013-03-27 17:55 ` sourceware.org@jan-o-sch.net
2013-03-27 20:51 ` mtk.manpages at gmail dot com [this message]
2014-06-13 18:35 ` fweimer at redhat dot com

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=bug-15312-131-bBGS1QWBtf@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).