From: Alejandro Colomar <alx.manpages@gmail.com>
To: Sam James <sam@gentoo.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 2/2] feature_test_macros.7: document _TIME_BITS
Date: Thu, 13 Oct 2022 21:17:30 +0200 [thread overview]
Message-ID: <7e1cc5d1-7d63-25b6-42f4-eefe6258f2de@gmail.com> (raw)
In-Reply-To: <1C02DD4E-3F55-4D7D-9D95-02B01F68A890@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 712 bytes --]
On 10/13/22 20:52, Sam James wrote:
>> Am I understanding this right? _FILE_OFFSET_BITS is required to be set for _TIME_BITS to be also set (in some archs)? Could you please link directly to a source for that in the commit log? They are somewhat related, but I'm quite surprised that something to do with file sizes interferes at all with something to do with time.
>>
>
> Yes, it's shocking, but true!
>
> I'll add a reference -- but it's in /usr/include/features-time64.h:
> https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/features-time64.h
O.O Yes, it seems to also be in the glibc documentation. Weird.
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-13 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:30 [PATCH v2 1/2] time_t.3type: reference _TIME_BITS Sam James
2022-10-13 18:30 ` [PATCH v2 2/2] feature_test_macros.7: document _TIME_BITS Sam James
2022-10-13 18:47 ` Alejandro Colomar
2022-10-13 18:52 ` Sam James
2022-10-13 19:17 ` Alejandro Colomar [this message]
2022-10-13 20:57 ` Sam James
2022-10-13 19:19 ` Alejandro Colomar
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=7e1cc5d1-7d63-25b6-42f4-eefe6258f2de@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=sam@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