[debian-mysql] Bug#1063738: mariadb: FTBFS on armel, armhf, powerpc, x32, hppa: size of array compile_time_assert is negative

[otto at debian.org]

Source: mariadb
Version: 1:10.11.7-1
Forwarded: https://jira.mariadb.org/browse/MDEV-33429
Tags: confirmed, help, ftbfs
User: debian-arm at lists.debian.org
Usertags: armel, armhf
X-Debbugs-CC: debian-arm at lists.debian.org
User: debian-powerpc at lists.debian.org
Usertags: powerpc
X-Debbugs-CC: debian-powerpc at lists.debian.org

After uploading latest MariaDB 10.11.7 to Debian it was noticed that the builds on armel, armhf, powerpc, x32, hppa fail on:

[ 31%] Building C object tests/CMakeFiles/bug25714.dir/bug25714.c.o
cd /<<PKGBUILDDIR>>/builddir/tests && /usr/bin/cc -DHAVE_CONFIG_H -DMYSQL_CLIENT -D_FILE_OFFSET_BITS=64 -I/<<PKGBUILDDIR>>/libmariadb/include -I/<<PKGBUILDDIR>>/builddir/libmariadb/include -I/<<PKGBUILDDIR>>/wsrep-lib/include -I/<<PKGBUILDDIR>>/wsrep-lib/wsrep-API/v26 -I/<<PKGBUILDDIR>>/builddir/include -I/<<PKGBUILDDIR>>/include/providers -I/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/client -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector --param=ssp-buffer-size=4 -O2 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing  -Wno-uninitialized -fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall -Wdeclaration-after-statement -Wenum-compare -Wenum-conversion -Wextra -Wformat-security -Wmissing-braces -Wno-format-truncation -Wno-init-self -Wno-nonnull-compare -Wno-unused-parameter -Wvla -Wwrite-strings -std=gnu99   -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT tests/CMakeFiles/bug25714.dir/bug25714.c.o -MF CMakeFiles/bug25714.dir/bug25714.c.o.d -o CMakeFiles/bug25714.dir/bug25714.c.o -c /<<PKGBUILDDIR>>/tests/bug25714.c
In file included from /<<PKGBUILDDIR>>/tests/mysql_client_fw.c:16,
                 from /<<PKGBUILDDIR>>/tests/mysql_client_test.c:38:
/<<PKGBUILDDIR>>/tests/mysql_client_fw.c: In function ‘main’:
/<<PKGBUILDDIR>>/include/my_global.h:384:18: error:
  384 |     typedef char compile_time_assert[(X) ? 1 : -1] __attribute__((unused)); \
      |                  ^~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/tests/mysql_client_fw.c:1438:3: note: in expansion of macro ‘compile_time_assert’
 1438 |   compile_time_assert(sizeof(MYSQL) == 77*sizeof(void*)+656);
      |   ^~~~~~~~~~~~~~~~~~~

See https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=armel&ver=1%3A10.11.7-1&stamp=1707544526&raw=0 and https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=armhf&ver=1%3A10.11.7-1&stamp=1707545871&raw=0 for full log. I was able to reproduce this on Launchpad.net armhf builder as well, both on Noble and Mantic, so it looks like a regression in MariaDB itself and not in any Debian dependency. These are all 32-bit systems, so it can be related to potential time_t changes in MariaDB.

This has been reported upstream in https://jira.mariadb.org/browse/MDEV-33429