Hello, lazy web.
So, I have a program that’s linked against glibc 2.1.3 (I think). My system has glibc 2.3.3, but that’s OK because glibc (since glibc 2.1) also provides the older (partly incompatible) ABIs, so already-built software keeps running. Opinions differ about that, but that’s another vague discussion that you can have elsewhere.
But the program can uses a shared-library plugin that I provide. But if I build this shared library on this system then it will be linked against glibc 2.3.3, and it would surely be bad for a program that uses glibc 2.1.3 to use a library that uses glibc 2.3.3. So, how can I tell the linker to use the older glibc ABI instead of the latest ABI that glibc has to offer?
I am (stupidly, but it makes things simpler for now) ignoring the possibility of API changes which would require me to compile against the older glibc headers.