Comment libc5 and libc6 coexistence (Score 1) 7
The issue is surely not really the libc5 and libc6 libraries themselves - a bit of fiddling with LD_LIBRARY_PATH and occasional wrapper scripts sorts that one out. And you can always find out which binaries require which library with ldd. In fact, I have a little perl auditer that tells you just which camp each executable is in.
The issue is really the run-time linker, and compatibility between glibc 2.0 and 2.1 that I can't find a satisfactory solution to, and no discussion I have yet seen has really resolved this one.
The issue is really the run-time linker, and compatibility between glibc 2.0 and 2.1 that I can't find a satisfactory solution to, and no discussion I have yet seen has really resolved this one.
