El 05/02/13 00:01, Linda Walsh escribió:
I get various programs that won't load because:
boot.msg:/usr/sbin/libvirtd: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /usr/lib64/libvirt.so.0) boot.msg:/usr/sbin/libvirtd: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib64/libvirt.so.0) boot.msg:Starting minidlna /usr/sbin/minidlna: /lib64/libm.so.6: version `GLIBC_2.15' not found (required by /usr/lib64/libvorbis.so.0)
and you did not see it coming do ya ? the glibc build system will scream (warn is not the proper word for what it does) at you when you try to do this and clearly tell that you will break your system in the process...
now it so happens that in my /lib64, I DO have a libc-2.15.so, libc-2.16.so and libc-2.17.so.
It's just that the default pointed to by libc.so.6 is the latest.
is the linker cache up to date ?
What I was trying to say was that if a program was out there that NEEDED a specific version of libc-2.XY.so,
then shouldn't it *link* to libc-2.XY.SO instead of of libc.so.6?
NO. The linker already adds proper versioned NEEDED entries to the DSOs.
My SW can't keep up!...
Am I supposed to ??
You are supposed to use ONE C library in your system, and there is no need to recompile or relink any software whatsoever.
When I talked about instability in the libc-series... people said I was fear mongering... but 3 incompat versions in 6 months? That's reasonable?
The library is OK, is compatible and doing exactly what it should, what has *always* done.. is your understanding and approach to the problem that is totally broken. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org