Toolchain updates broke GLIBC support for Linux #943
Description
Toolchain updates broke GLIBC support for Linux.
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /root/mtaserver/x64/deathmatch.so)
ERROR: Loading mod (/root/mtaserver/x64/deathmatch.so) failed!
Reproduction:
- get Linux server r16641 (last known working build)
- update that build to r16705 (introduction of issue) or just latest
At least reproducable on: Debian 9 (ships GLIBC 2.24-11+deb9u4); not sure if relevant
Expected behavior: updating MTA server build should never result in breaking compatibility/a total block, no matter the Linux distribution or local GLIBC version (when it worked prior to the changes in r16705).
If further investigation points this way, we should evaluate if it's appropiate for MTA server to refuse operation on Linux servers without updated GLIBC version. It seems to be less than ideal; for example, the latest Debian release doesn't ship 2.27. Although, something with patching was mentioned (see below) of which feature I don't know the technical details.. I believe that is, MTA server forces any distribution to inherit MTA's glibc version rather than the native, which then became bugged due to the update.
@sbx320's thoughts on this issue:
sbx320 [7:38 PM]
that glibc patching might've been broken by the gcc 8 update
Probably some new symbol version was introduced for something that we don't patch yet
CC: @Jusonex (suspected commit: 8be9c1d)