You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, the minimal GLIBC version supported by the Tebako package is the GLIBC version on the system where the package was created. While patchelf enables forward compatibility, it does not ensure backward compatibility.
Currently, we provide an Ubuntu 20 container, which requires a minimum GLIBC version of 2.31. By default RHEL7 has GLIBC 2.17, RHEL8 has GLIBC 2.28.
If the question is, "Is it possible to create a Tebako container that produces GLIBC 2.17-compatible binaries?" the answer is "probably yes". To achieve this, we would need to base the build environment on RHEL7 and address any compatibility issues with folly and dwarfs, which may take a few months.
In short, the minimal GLIBC version supported by the Tebako package is the GLIBC version on the system where the package was created. While
patchelf
enables forward compatibility, it does not ensure backward compatibility.Currently, we provide an Ubuntu 20 container, which requires a minimum GLIBC version of 2.31. By default RHEL7 has GLIBC 2.17, RHEL8 has GLIBC 2.28.
If the question is, "Is it possible to create a Tebako container that produces GLIBC 2.17-compatible binaries?" the answer is "probably yes". To achieve this, we would need to base the build environment on RHEL7 and address any compatibility issues with folly and dwarfs, which may take a few months.
Originally posted by @maxirmx in tamatebako/tebako#207 (comment)
The text was updated successfully, but these errors were encountered: