linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] fts.3 is not available in LFS builds
Date: Sat, 15 Mar 2014 06:54:16 -0700	[thread overview]
Message-ID: <20140315135416.GA10430@infradead.org> (raw)

As pointed out during a recent discussion on libc-hacker the fts(3)
APIs can't be used with large file offsets:

	https://sourceware.org/bugzilla/show_bug.cgi?id=15838

The manpage should mention this.  Note: the text probably needs some
better formatting at least, but I couldn't come up with proper markup
for compiler arguments.

Signed-off-by: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>

diff --git a/man3/fts.3 b/man3/fts.3
index 9374463..2b14c0d 100644
--- a/man3/fts.3
+++ b/man3/fts.3
@@ -774,6 +774,10 @@ The options were invalid.
 These functions are available in Linux since glibc2.
 .SH CONFORMING TO
 4.4BSD.
+.SH BUGS
+All the APIs described in this manpage are not safe when compiling
+a program using the LFS APIs, e.g. by using
+-D_FILE_OFFSET_BITS=64.
 .\" The following statement is years old, and seems no closer to
 .\" being true -- mtk
 .\" The
--
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:[~2014-03-15 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 13:54 Christoph Hellwig [this message]
     [not found] ` <20140315135416.GA10430-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-15 14:47   ` [PATCH] fts.3 is not available in LFS builds Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAkgqXUf0yWaXyAD7yBJgivp9Jmwvz4EAnh_DpyActuoGwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-16 17:22       ` Christoph Hellwig
     [not found]         ` <20140316172219.GA16900-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-17 13:56           ` Michael Kerrisk (man-pages)
     [not found]             ` <5326FF14.7010305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-17 14:01               ` Christoph Hellwig
     [not found]                 ` <20140317140118.GA11576-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-17 14:02                   ` Michael Kerrisk (man-pages)
     [not found]                     ` <CAKgNAkh7ES18jT2coD39ZXvjUxkrZavaG=SufNS_-16SgM3kUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-17 14:06                       ` Christoph Hellwig
     [not found]                         ` <20140317140616.GA15958-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-17 14:11                           ` Michael Kerrisk (man-pages)
     [not found]                             ` <CAKgNAkinnsvoXT_FNxaS7L5Umo6va8OCVnTv-gZ5vvVSFi2--w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-19  3:12                               ` Mike Frysinger
2014-03-19  5:56                                 ` Mike Frysinger
2014-03-19 13:29                                   ` Michael Kerrisk (man-pages)
2014-03-19 13:29                                 ` Michael Kerrisk (man-pages)

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=20140315135416.GA10430@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@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).