Hi! While working on MariaDB 10.11.7 I am seeing the compilation fail on all 32-bit systems with error: size of array ‘compile_time_assert’ is negative Considering this affects all 32-bit systems and error message is about time, sounds like it could be related to 64-bit time, but seems MDEV-32188 wasn't merged yet. Does anybody remember off the top of their head any other time related changes in latest release that maybe aren't 32-bit compatible? Tracking in https://jira.mariadb.org/browse/MDEV-33429 On Sat, 3 Feb 2024 at 21:25, Otto Kekäläinen <otto@kekalainen.net> wrote:
Hello!
Does MariaDB already fully support 64-bit time_t (the year 2038 problem)?
MariaDB 10.11 was today uploaded to Debian experimental without any 64-bit time_t support changes, just a library name change[1] to test that it works with the Debian 64-bit time_t tooling as Debian is currently undergoing a transition to it[2]. So far MariaDB built successfully and passed the main MTR suite on 11 architectures[3].
Monty mentioned that some work is in progress, and indeed I found his commits in two branches [4,5] but looking at the commits and their link to buildbot it seems they are not passing the CI. I also found one MDEV[6] to make TIMESTAMP use the whole 32-bit unsigned range.
Are there any other efforts in progress?
Does MTR main suite include tests for 64-bit time support? Should MTR automatically currently fail if toolchain time is 64-bit?
[1] https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/063109a306a016... [2] https://lists.debian.org/debian-devel-announce/2024/02/msg00000.html [3] https://buildd.debian.org/status/package.php?p=mariadb&suite=experimental [4] https://github.com/MariaDB/server/commits/bb-11.4-timestamp/ [5] https://github.com/MariaDB/server/commits/bb-11.4-monty/ [6] https://jira.mariadb.org/browse/MDEV-32188