Message ID | 20230626162203.3643572-2-richard.purdie@linuxfoundation.org |
---|---|
State | Accepted, archived |
Commit | b9e0c5e750c3097e176fdc18b3b58b622f716e71 |
Headers | show |
Series | [1/2] time64: Disable CFLAGS for strace | expand |
diff --git a/meta/conf/distro/defaultsetup.conf b/meta/conf/distro/defaultsetup.conf index f6894f3ab56..1abb5096293 100644 --- a/meta/conf/distro/defaultsetup.conf +++ b/meta/conf/distro/defaultsetup.conf @@ -2,7 +2,7 @@ include conf/distro/include/default-providers.inc include conf/distro/include/default-versions.inc include conf/distro/include/default-distrovars.inc include conf/distro/include/maintainers.inc - +include conf/distro/include/time64.inc require conf/distro/include/tcmode-${TCMODE}.inc require conf/distro/include/tclibc-${TCLIBC}.inc
There is a problem with 32 bit time looming for many 32 bit platforms including arm, mip32, powerpc and x86 (but not riscv32) in 2038 when the 32 bit field time_t can no longer store the time value correctly due to overflow. Preparing for this is tricky as the ABI between libraries and binaries will change and it isn't possible to migrate easily as structures and return values change size. As we're a source based system, the project has taken the decision that we should change the compiler flags to switch to both largefile and 64 bit time_t. With OE-Core we've ironed out the issues we could spot apart from some testing issues in strace and lttng-tools for which discussions are ongoing upstream. There is more testing to be done but we wanted to make this switch now in good time before our next LTS release so we can work through any issues arrising. We had already tried to mandate largefile everywhere before this but this gives an opportunity to ensure that at the same time. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- meta/conf/distro/defaultsetup.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)