[debian-mysql] Bug#972564: Acknowledgement (mariadb-10.5: FTBFS on armhf: compiler seems to segfault with libnuma enabled?)

Otto Kekäläinen otto at debian.org
Tue Oct 27 07:30:17 GMT 2020


Control: retitle -1 mariadb-10.5: FTBFS on armhf: compiler seems to segfault

I compared the latest (still failing) armhf build
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=armhf&ver=1%3A10.5.6-2&stamp=1603737750&raw=0
with the last build that passed
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=armhf&ver=1%3A10.5.5-3&stamp=1602238411&raw=0

These dependencies had updates between the builds:
bison 2:3.7.2+dfsg-1 -> 2:3.7.3+dfsg-1
cmake-data 3.18.2-1 -> 3.18.4-1
libxml2:armhf 2.9.10+dfsg-6 -> 2.9.10+dfsg-6.1
libldap-2.4-2:armhf 2.4.53+dfsg-1 -> 2.4.54+dfsg-1
cmake 3.18.2-1 -> 3.18.4-1
libglib2.0-0:armhf 2.66.0-2 -> 2.66.1-2
dh-apparmor 2.13.4-3 -> 2.13.5-1
libsystemd-dev:armhf 246.6-1 -> 246.6-2

Also indirect dependency:
libc-bin 2.31-3 -> 2.31-4

The C compiler identification was in both builds GNU 10.2.0.

The upstream MariaDB 10.5.6 was a security release with minimal
changes. Most likely this armhf build regression is caused by some of
the dependencies that upgraded and changed behaviour in some way. The
GCC folks already confirmed they can reproduce the issue, but it is
still unclear if GCC was the root cause here or not.



More information about the pkg-mysql-maint mailing list