Caused by: java.lang.UnsatisfiedLinkError: /tmp/jna/jna2123156991551141605.tmp: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by /tmp/jna/jna2123156991551141605.tmp)
Hi, I attempted to use libpam4j 1.7 (jna 3.5.0) on a Centos 5.8 x86_64, with glibc2.5 installed, but received the "GLIBC_2.11" not found error. The same code worked on a Centos 5.5 x86 (32bit) with glibc2.5.
I downgraded to libpam4j 1.5 (jna 3.2.2), and the problem went away (but was still present in 1.6 with jna 3.3.0).
Hi, I attempted to use libpam4j 1.7 (jna 3.5.0) on a Centos 5.8 x86_64, with glibc2.5 installed, but received the "GLIBC_2.11" not found error. The same code worked on a Centos 5.5 x86 (32bit) with glibc2.5.
I downgraded to libpam4j 1.5 (jna 3.2.2), and the problem went away (but was still present in 1.6 with jna 3.3.0).
I believe this is a JNA issue. I saw a Jenkins bug report of the same problem, where the solution seemed to have been a rebuilt JNA: https://issues.jenkins-ci.org/browse/JENKINS-10354?actionOrder=asc
I wanted to report that downgrading to libpam4j 1.5 fixed it, however.