valkey-glide: java.lang.UnsatisfiedLinkError linking libc

SBT Dependency

“io.valkey” % “valkey-glide” % “1.3.0” classifier “linux-x86_64”

Error

java.lang.UnsatisfiedLinkError: /tmp/nativeutils879005385204760/libglide_rs.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/nativeutils879005385204760/libglide_rs.so)

	at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
	at java.base/java.lang.ClassLoader$NativeLibrary.load(ClassLoader.java:2442)
	at java.base/java.lang.ClassLoader$NativeLibrary.loadLibrary(ClassLoader.java:2498)
	at java.base/java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2694)
	at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2627)
	at java.base/java.lang.Runtime.load0(Runtime.java:768)
	at java.base/java.lang.System.load(System.java:1834)
	at glide.ffi.resolvers.NativeUtils.loadLibraryFromJar(NativeUtils.java:105)
	at glide.ffi.resolvers.NativeUtils.loadGlideLib(NativeUtils.java:44)
	at glide.ffi.resolvers.SocketListenerResolver.<clinit>(SocketListenerResolver.java:11)
	at glide.api.BaseClient.buildChannelHandler(BaseClient.java:472)
	at glide.api.BaseClient.createClient(BaseClient.java:367)
	at glide.api.GlideClusterClient.createClient(GlideClusterClient.java:105)

System Info

ldd --version ldd (Ubuntu GLIBC 2.31-0ubuntu9) 2.31
Copyright © 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

lsb_release -a Distributor ID: Pop
Description: Pop!_OS 20.04 LTS
Release: 20.04
Codename: focal

lscpu Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 46 bits physical, 48 bits virtual
CPU(s): 20
On-line CPU(s) list: 0-19
Thread(s) per core: 2
Core(s) per socket: 10
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel® Core™ i9-9820X CPU @ 3.30GHz

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 18 (10 by maintainers)

Most upvoted comments

You can build in Docker like the example repo I made and linked above. It would use the image glibc and make 20.04 and many others available I believe.

On Wed, Feb 26, 2025 at 3:37 AM Avi Fenesh @.***> wrote:

When you have glibc 33 a machine with glibc will work because 35 “includes” 33. So we need to build on 20. We need to keep building on the lowest lts, or when building the rust to set the target which is possible with rust. When I develop locally, i change the target to check if it compiles. Another option is keeping the CI on what is available by GH, and running the CD on the ephemerals.

In each case we need to take this task and test it now, before we get to a real release.

— Reply to this email directly, view it on GitHub https://github.com/valkey-io/valkey-glide/issues/3218#issuecomment-2684286814, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRMQUNJWNPYLRBYT2BAHWL2RV4NZAVCNFSM6AAAAABXRN2RN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBUGI4DMOBRGQ . You are receiving this because you were mentioned.Message ID: @.***> [image: avifenesh]avifenesh left a comment (valkey-io/valkey-glide#3218) https://github.com/valkey-io/valkey-glide/issues/3218#issuecomment-2684286814

When you have glibc 33 a machine with glibc will work because 35 “includes” 33. So we need to build on 20. We need to keep building on the lowest lts, or when building the rust to set the target which is possible with rust. When I develop locally, i change the target to check if it compiles. Another option is keeping the CI on what is available by GH, and running the CD on the ephemerals.

In each case we need to take this task and test it now, before we get to a real release.

— Reply to this email directly, view it on GitHub https://github.com/valkey-io/valkey-glide/issues/3218#issuecomment-2684286814, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRMQUNJWNPYLRBYT2BAHWL2RV4NZAVCNFSM6AAAAABXRN2RN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBUGI4DMOBRGQ . You are receiving this because you were mentioned.Message ID: @.***>

@nkconnor the note about musl is still in place, and currently I’m exploring some options to reduce platform-specific dependency as a whole for the java client, by replacing some internal logic to an alternate design. As long as we hard-code the version we build on, instead of using “latest” it will result in the same GLIBC. The GLIBC is minimal, meaning, if you have a higher version, it will work for you, since each version is “includes” the previous. But, when Ubuntu drops LTS, and move to ESM, we will likely drop support as well. It will be part of a major release with a noticeable announcement. We are trying hard to avoid breaking changes, and doing so, if necessary, will happen just as part of a major release. But support means that we run a large matrix of valkey versions, language versions, and host versions. So while some other targets may be supported, we can “state” just what we tested by the CI, and each version is inflating the CI a lot. But we are talking on about 2–3 years from now, in case that the user itself is using at least 5-year-old OS version and doesn’t want to upgrade. Which, in that case, we will be just pips in a line of incompatibility of the user machine.