3 ms·
Having two versions of libc installed is not the problem. The problem is when you link to two different libraries in your app that link to two different (and AB
by int_19h 5y ago
Having two versions of libc installed is not the problem. The problem is when you link to two different libraries in your app that link to two different (and ABI-incompatible) versions of libc.
- tedunangst 5y agoVersioning doesn't solve that problem. I call time() in my new code. I call some library which eventually calls futimes(). Everybody along the way needs to agree on the size of time_t. The library can't correctly use the old symbol even if it's available.
- int_19h 5y agoOn Linux, you're correct, but only because the symbol namespace is global. On Windows, every DLL with a different name also has its own distinct symbol namespace. Thus, the conflict you describe can only arise if your code explicitly propagates some time_t* value from one library to the other.