Gold Source servers need a Glibc check

[dgibbs64]

Working on a Gold source server and found with check-glibc that we might need to increase to glibc requirements. The increase is caused by steamclient.so

GLIBC_2.14

GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/demoplayer.so
GLIBC_2.2.4: /home/lgsm/bbserver/serverfiles/libgcc_s.so.1
GLIBC_2.3.2: /home/lgsm/bbserver/serverfiles/libtier0.so
GLIBC_2.12: /home/lgsm/bbserver/serverfiles/steamclient.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/voice_speex.so
GLIBC_2.2: /home/lgsm/bbserver/serverfiles/vgui2.so
GLIBC_2.7: /home/lgsm/bbserver/serverfiles/engine_i486.so
GLIBC_2.2: /home/lgsm/bbserver/serverfiles/libvstdlib.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/vgui.so
GLIBC_2.14: /home/lgsm/bbserver/serverfiles/linux64/steamclient.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/core.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/filesystem_stdio.so
GLIBC_2.3.2: /home/lgsm/bbserver/serverfiles/crashhandler.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/brainbread/dlls/bb.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/libsteam_api.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/valve/dlls/director.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/valve/dlls/hl.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/valve/cl_dlls/client.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/proxy.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/voice_silk.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/cstrike/dlls/cs.so
GLIBC_2.2.5: /home/lgsm/bbserver/serverfiles/cstrike/dlls/cs_amd64.so
GLIBC_2.3: /home/lgsm/bbserver/serverfiles/cstrike/cl_dlls/client.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/hlds_linux
GLIBC_2.3.2: /home/lgsm/bbserver/serverfiles/libstdc++.so.6
GLIBC_2.3.2: /home/lgsm/bbserver/serverfiles/libsteam.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/voice_miles.so
GLIBC_2.1.3: /home/lgsm/bbserver/serverfiles/hltv

[dgibbs64]

2.14 is now the standard because of steamCMD requirements

[dgibbs64]

SteamCMD can run on CentOS 6 which is GLIBC 2.12

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.