The safe solution would be to check for a sample of the expected symbols
in glibc in configure, but I'm not sure it's worth it. I doubt anyone
builds with an older glibc than we do at Oracle, but you never know.
/Erik
On 9/18/25 00:15, Baesken, Matthias wrote:
( seems some versions of RHEL 7 / SLES 12 still had those old glibc
versions)
Could we clean this up?
Or is there still some need to support this in jdk26 ?
I always find it very difficult to determine when checks like these
become unnecessary. I think RHEL 7 with glibc 2.17 is the oldest Linux
release we currently support.
Given I wrote the above in April 2021, I would hope we can now move on,
but again I don't know how to readily determine that.
I could create a removal PR and maybe you can test on the oldest platforms you
want to support in release 26 ?
Best regards, Matthias
