https://github.com/MariaDB/buildbot/pull/143

Hi smtalk,

We didn't yet get arm tarballs packages done, however we have expanded the supported ARM rpm and deb packages.

It is still in the pipeline.

Any news on this? It seems it was planned in 2020: "The next MariaDB release will include additional binary tarballs for ARM distributions, in addition to the already existing RPM and DEB packages." (https://mariadb.org/arm-improvements-in-2020/)

Centos6 isn't supported any more surely. The highly colourful page https://c6eol.centos.org/ says so.

So you still want glibc dynamicly linked? Any reason why? A static linking of that too will provide a high level of optimizations that have been provided for arm64 over the years. If we do it that we we only need to support a minimum Linux kernel version (3.14?) or so based on some 10.5 commits I did in the very early cycle. (MDEV-16548)

If dynamic:

glibc-2.17 on centos7. I haven't exhaustively searched yet.

https://distrowatch.com/dwres.php?firstlist=debian&secondlist=centos&firstversions=4&secondversions=1&resource=compare-packages&view=major&refresh=Refresh

danblack This is the task that covers us releasing ARM tarballs with as many statically compiled system components as possible.

The goal of tarballs is for them to be as portable as possible on any system. The container that builds these tarballs needs to be the system that has the oldest possible glibc that is still maintained when we first publish these packages. Most likely CentOS 6's glibc version.