java.lang.UnsatisfiedLinkError /lib64/libc.so.6: version `GLIBC_2.11' not found about jna HOT 9 CLOSED

updated linux binaries for x86/amd64 against 2.1.3 and 2.2.5, respectively.

from jna.

I think I just got this same error message from jnaerator with its "shaded" jar. Guess I'll put the newer jna.jar first in the classpath for now...

from jna.

no. the binaries have been checked in but not yet tagged or released

On Feb 16, 2012, at 4:13 PM, Roger Pack wrote:

has this been released yet? I still seem to be getting it with the 3.4.0 binaries linked to here: https://github.com/twall/jna

---

Reply to this email directly or view it on GitHub:
#52 (comment)

from jna.

I'm also facing this bug. Do you plan to release a new JNA version anytime soon ?

from jna.

It was waiting on someone to review and/or fix the maven release bits, but no one has stepped forward.

If that situation continues, I can tag and release next week sometime. That said, a working version is available from the repo at any time.

T.

On May 4, 2012, at 6:12 AM, Zlika wrote:

I'm also facing this bug. Do you plan to release a new JNA version anytime soon ?

---

Reply to this email directly or view it on GitHub:
#52 (comment)

from jna.

I use maven, so I try to only use the versions that are on maven central (with an "official" numbering).

from jna.

Same problem on 3.5.0. Last version that works on RHEL5 is 3.3.0

from jna.

If you need to specifically target older releases, you might want to build your own.

I don't have any older 64-bit build platforms.

On Oct 20, 2012, at 7:07 AM, Maxim Valyanskiy wrote:

Same problem on 3.5.0. Last version that works on RHEL5 is 3.3.0

—
Reply to this email directly or view it on GitHub.

from jna.

Well, I understand that the latest JNA has been build against a fresh updated OS.
JNA is a great package that has served us very well.

Nevertheless, we have this issue and it is not so simple to upgrade our machines.
When I checked JDK 7u5, it requires GLIBC 2.5.

Currently, you have a case in which backward compatibility breaks:

• A system S with GLIBC 2.5+ (< 2.11) runs OK with older version of JNA and JDK 7u5
• Someone starts using JNA latest on S
• JNA latest claims it works with JDK7u5 but fails to run properly.

The cleanest approach would be:

• check which Java versions (update including) you want to claim JNA compatible with,
• check which GLIBC versions they support
• make sure JNA support those.
• for all other Java updates/versions, make conditional notice in the release notes that the OS has to be newer than some version (currently GLIBC 2.11)

If you don't do this, you will be loosing clients from all kinds of conservative installations such as long support Debian and BSD clones, who do not want to unnecessarily upgrade something that works rather well.

from jna.