From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Florian Weimer <fweimer@redhat.com>, bug-gnulib@gnu.org
Subject: Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64
Date: Tue, 06 Jul 2021 03:34:53 +0200 [thread overview]
Message-ID: <3476521.qdJYWE5AFN@omega> (raw)
In-Reply-To: <80b0b2e9-fe2d-f11d-7644-058220394237@cs.ucla.edu>
Hi Paul,
> There is a way to build with 32-bit time_t even in Gnulib-using apps,
> so distros wanting to stick with 32-bit time_t can build Gnulib-using
> apps with the appropriate flags so that they're still living in the
> 32-bit time_t world for now.
What are these appropriate flags?
I'd like to understand
- whether these flags are simple or complicated,
- whether we really do need a module dependency 'largefile' -> 'year2038',
- how to best document these things. (Btw, currently these are two sections
in the chapter "Native Windows Support". I should reorganize this.)
Bruno
next prev parent reply other threads:[~2021-07-06 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 2:33 [PATCH] year2038: support glibc 2.34 _TIME_BITS=64 Paul Eggert
2021-07-02 15:32 ` Florian Weimer
2021-07-02 22:29 ` Bruno Haible
2021-07-03 2:40 ` Paul Eggert
2021-07-05 14:32 ` Florian Weimer
2021-07-05 20:14 ` Paul Eggert
2021-07-06 1:34 ` Bruno Haible [this message]
2021-07-06 22:29 ` Paul Eggert
2021-07-06 2:11 ` Bruno Haible
2021-07-07 8:45 ` Florian Weimer
2021-07-07 21:58 ` Paul Eggert
2021-07-08 5:36 ` Florian Weimer
2021-07-17 3:39 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3476521.qdJYWE5AFN@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
/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).