After upgrading to glibc 2.1 with symbol versioning I get errors about undefined symbols. What went wrong?
{AJ} The problem is caused either by wrong program code or tools. In the versioned libc a lot of symbols are now local that were global symbols in previous versions. It seems that programs linked against older versions often accidentally used libc global variables — something that should not happen. The only way to fix this is to recompile your program. Sorry, that’s the price you might have to pay once for quite a number of advantages with symbol versioning.
Related Questions
- I get undefined symbol errors like /usr/kde/3.3/lib/libartskde.so.1: undefined symbol: _ZTv0_n32_N4Arts16SynthModule_stub11autoSuspendEv. What can I do?
- After upgrading to glibc 2.1 with symbol versioning I get errors about undefined symbols. What went wrong?
- Is the Cross the Wrong Symbol for Christians?
