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 issue #812 , the old method for keeping runtime compatibility of glibc 2.12 doesn't work when building against the modern glibc (>=2.34). #812 rollback to another combination: runtime glibc >= 2.17, build on ubuntu 20.04.
I think it could be possible to move to a better one: runtime glibc >= 2.12 and build on ubuntu 22.04 (glibc = 2.35).
PS: The output native image requires pthread_setname_np api, which first appeared in glibc 2.12, so this the least version for now.
The text was updated successfully, but these errors were encountered:
…823)
The modern glibc from 2.34 had two breaking changes: move all api in lib{pthread,dl,rt}.so into libc.so, new static start up code breaking the runtime compatibility for old glibc (<2.34). See https://developers.redhat.com/articles/2021/12/17/why-glibc-234-removed-libpthread for more info.
This commit has 3 changes to overcome these changes:
- override gcc path to redefine glibc symbols on the fly in the generated .o by graalvm when linking
- provide a dynamic startup code to support both old and modern runtime glibc
- add needed dynamic libraries: lib{pthread,rt,dl}.so.
In issue #812 , the old method for keeping runtime compatibility of glibc 2.12 doesn't work when building against the modern glibc (>=2.34). #812 rollback to another combination: runtime glibc >= 2.17, build on ubuntu 20.04.
I think it could be possible to move to a better one: runtime glibc >= 2.12 and build on ubuntu 22.04 (glibc = 2.35).
PS: The output native image requires
pthread_setname_np
api, which first appeared in glibc 2.12, so this the least version for now.The text was updated successfully, but these errors were encountered: