> On 31 Oct 2022, at 10:37, Mickaël Bucas <[email protected]> wrote: > > Le dim. 30 oct. 2022 à 16:48, Sam James <[email protected]> a écrit : >> >> Signed-off-by: Sam James <[email protected]> >> --- >> eclass/flag-o-matic.eclass | 13 +++++++++++++ >> 1 file changed, 13 insertions(+) > >> +# @FUNCTION: append-time64-flags >> +# @DESCRIPTION: >> +# Add flags that enable 64-bit time_t. Implies Large File Support >> +# (calls append-lfs-flags) automatically.
> Hello Sam > Hi Mickaël, > As a simple user, can you explain to me or point me to a resource > about the link between Large File Support and time64 configuration ? > This is a good question -- the answer is two-fold: 1. glibc requires LFS to enable time64 2. Both can involve an ABI break if an off_t or time_t for example are in an exposed structure, so it's best to do them at the same time. But I've had second thoughts about this and I want to rethink if we want to take this approach in the patch I sent. I think we may want to do a hard-switch for defaults instead in new profiles. I need to reflect on it a bit more. Plans and notes are at https://wiki.gentoo.org/wiki/Project:Toolchain/time64_migration if interested! > Thanks > Best regards > Best, sam
signature.asc
Description: Message signed with OpenPGP
