Building for an outdated x86_64 Linux target machine

[fabalthazar]

Hi,

I am designing a C++ app to run on an outdated embedded Linux system (GCC 9, binutils 2.34, kernel 5.4, glibc 2.31) that I cannot change.

The app built with the up-to-date toolchain from my host PC refuses to run on the target because of Glibc versions incompatibilities.

My first approach was to generate a toolchain with crossdev with fixed outdated tools versions. This works quite good except the toolchain refuses to be multilib and I would like it to be.

[Genone]

The easiest option would probably be setup a full chroot that mirrors your target environment and build your app within that.

If glibc is the only issue that prevents you from using your regular toolchain then (in theory) you should be able to link against the symbols of the same version as your target glibc (see https://stackoverflow.com/questions/2856438/how-can-i-link-to-a-specific-glibc-version). However messing with symbol versioning usually results in total chaos in my experience as it basically only used by glibc and documentation/support is sparse.