From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Cyril Hrubis <chrubis@suse.cz>, Jeff Layton <jlayton@redhat.com>
Cc: mtk.manpages@gmail.com, Florian Weimer <fweimer@redhat.com>,
Mike Frysinger <vapier@gentoo.org>,
libc-alpha@sourceware.org, linux-fsdevel@vger.kernel.org,
Carlos O'Donell <carlos@redhat.com>,
Yuriy Kolerov <Yuriy.Kolerov@synopsys.com>
Subject: Re: [glibc PATCH] fcntl: put F_OFD_* constants under #ifdef __USE_FILE_OFFSET64
Date: Tue, 23 Aug 2016 21:11:00 -0000 [thread overview]
Message-ID: <8acbfa50-516f-d402-928f-9a391610557d@gmail.com> (raw)
In-Reply-To: <20160823113830.GB4962@rei.suse.cz>
On 08/23/2016 11:38 PM, Cyril Hrubis wrote:
> Hi!
>> To be clear, that approach was NAK'ed by Christoph (and I think that's
>> a good thing, actually -- one more nail in the non-LFS coffin). I think
>> what we want merged into glibc is this patch that I sent late on
>> Thursday:
>>
>> [glibc PATCHv2] fcntl: don't define OFD lock constants for 32-bit builds with small file offsets
>>
>> We'll also need your patch to the fcntl(2) manpage as well, but that's
>> a separate problem.
>
> Hmm, the patch for man-pages should be updated as well. We need
> somethign as:
>
> ...
> This lock type is Linux-specific, and available since Linux 3.15.
> On 32bit platform _FILE_OFFSET_BITS must defined to 64 (before including
> any header files) to make these locks available.
> ...
>
> Michael should I send updated patch or will you take care of this?
I can do it, or you can. At the moment, I'm just holding off until I
see what is accepted into glibc.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-08-23 21:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:47 Jeff Layton
2016-08-17 15:44 ` Joseph Myers
2016-08-17 17:50 ` Jeff Layton
2016-08-17 17:57 ` Joseph Myers
2016-08-17 18:23 ` Jeff Layton
2016-08-17 16:13 ` Mike Frysinger
2016-08-17 17:34 ` Florian Weimer
2016-08-17 17:40 ` Jeff Layton
2016-08-17 18:02 ` Florian Weimer
2016-08-17 18:21 ` Jeff Layton
2016-08-17 18:51 ` Florian Weimer
2016-08-17 19:20 ` Jeff Layton
2016-08-18 8:44 ` Florian Weimer
2016-08-18 8:59 ` Andreas Schwab
2016-08-17 20:52 ` Andreas Schwab
2016-08-18 8:45 ` Florian Weimer
2016-08-17 18:43 ` Mike Frysinger
2016-08-17 19:15 ` Jeff Layton
2016-08-17 19:59 ` Michael Kerrisk (man-pages)
2016-08-17 20:05 ` Jeff Layton
2016-08-17 20:37 ` Mike Frysinger
2016-08-17 20:58 ` Jeff Layton
2016-08-17 21:35 ` Mike Frysinger
2016-08-17 21:48 ` Jeff Layton
2016-08-18 9:00 ` Florian Weimer
2016-08-23 11:09 ` Cyril Hrubis
2016-08-23 11:36 ` Jeff Layton
2016-08-23 11:43 ` Cyril Hrubis
2016-08-23 21:11 ` Michael Kerrisk (man-pages) [this message]
2016-11-14 13:45 ` Cyril Hrubis
2016-11-22 18:41 ` Florian Weimer
2016-08-18 8:57 ` Florian Weimer
2016-08-17 20:03 ` Mike Frysinger
2016-08-17 21:35 ` Cyril Hrubis
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=8acbfa50-516f-d402-928f-9a391610557d@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=Yuriy.Kolerov@synopsys.com \
--cc=carlos@redhat.com \
--cc=chrubis@suse.cz \
--cc=fweimer@redhat.com \
--cc=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=vapier@gentoo.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).