[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64
From: |
Bruno Haible |
Subject: |
Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64 |
Date: |
Tue, 06 Jul 2021 03:34:53 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-210-generic; KDE/5.18.0; x86_64; ; ) |
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
- [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Paul Eggert, 2021/07/01
- Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Florian Weimer, 2021/07/02
- Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Bruno Haible, 2021/07/05
- Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Florian Weimer, 2021/07/07
- Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Paul Eggert, 2021/07/07
- Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Florian Weimer, 2021/07/08
- Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64, Paul Eggert, 2021/07/16