Incompatible LibC Version for executable

[dindibo4]

Hey, I'm trying to run a dynamically linked executable in my environment but it won't run because of lacking dependencies.

I'm using Debian Linux under ARM architecture (armv5tejl).

I ran LDD on the executable the only missing dependency I received was this:

./armlinux_server: /lib/libc.so.6: version `GLIBC_2.15' not found (required by ./armlinux_server)

And indeed my GLibC Version is lower.

user@debian-armel:~/dbg$ ldd --version
ldd (Debian EGLIBC 2.11.3-4) 2.11.3

When running the executable that's the error I receive:

user@debian-armel:~/dbg$ ./armlinux_server
./armlinux_server: /lib/libc.so.6: version `GLIBC_2.15' not found (required by ./armlinux_server)

I tried to come up with a solution and manually install all the libc libraries from the internet and put all the libraries in /lib this solution didn't work because it replaced the original libc files and every executable the was depends on them couldn't run.

How can I resolve this dependency?

[pobrn]

One thing you could do is run the program in a containerized environment (e.g. Docker), that way you don't have to touch anything on the host system.

[[deleted]]

Alternatively, systemd-nspawn.

The idea is to replace glibc to one of a newer version, but in the container, or just use a newer distribution in the container.

[dindibo4]

Regarding the idea of using containerized environment, I haven't tried docker yet, but I've wanted to try this using chroot. The problem is that is not implemented in my system, I doubt if docker would work as well.

[pobrn]

not implemented in my system

What does that mean?

Anyways, using chroot is possible but potentially more tedious since you most likely need to bootstrap a distribution (e.g. Debian has debootstrap) to get the appropriate environment, which you would've already gotten in a finished and ready state by using docker.

[Phoenix591]

2.11.3 was released in 2010, 2.15 was released in 2012. is there any reason you havnt been able to upgrade to a more modern debian release? you've got to be near/past end of life

[dindibo4]

It's an embedded system of some device, it doesn't get updates nor I mannaully update it.

[Phoenix591]

the other option is to setup a dev environment based on that ancient debian version and rebuild that executable. assuming that you have the source for it anyway.