Jan Engelhardt wrote:
On Saturday 2013-01-12 20:40, Linda Walsh wrote:
Starting with the 12.X series, it seems the problem has gotten significantly worse. Binaries from each of the 12.x versions are often mutually incompatible -- most often because each version has been hard-coded to accept only 1 version of GLIBC.
Nonsense.
This is not "exact" but "greater-than", because libraries never remove version symbols (like GLIBC_2.14) while the SONAME stays the same.
Ah...you are right... I remember the problem. Basic system functions and libs were moved into unmounted partitions -- the most heinous being *mount*. Without that I can't mount /usr to access the rest. Is there a reason why it can't be in /bin with a symlink in /usr/bin/? For that matter -- any of the files that are being moved from /{bin,sbin,lib,lib64} -> /usr, wouldn't it be possible to move them back to /being on "/" instead of under /usr? Then /usr can have symlinks -- because if /usr is there, then "/" will always be there, but the presence of "/" doesn't mean /usr has been mounted yet. I had to go back to glib2.14, or my system wouldn't boot. Then I kept getting lots of error messages like: `/usr/lib64/libvirt/virt-aa-helper: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib64/libvirt/virt-aa-helper)' prelink: /usr/bin/virsh: Could not parse `/usr/bin/virsh: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib64/libvirt.so.0)' prelink: /usr/bin/virt-viewer: Could not parse `/usr/bin/virt-viewer: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib64/libvirt.so.0)' (except it was GLIBC_2.15... I used to be able to install higher level libraries and **usually** have them work just fine -- but with a hard-coded symbol in the binary, that's no longer possible. Are you saying ALL programs use the new GLIBC features, as that used to not be the case. Is this because the paths are hard coded into the libs and utilities (comment to that effect in GLIBC in finding nscd...)... doesn't seem to use PATH, but a hard coded value... So now with glibc-2.15, I won't be able to reboot my system w/out a rescue disk. What got worse in the 12.x series was the inclusion of the glibc version in the binaries. Before that wasn't the case, so I could try newer packages to see if they worked (always did with pre-reqs installed)...But requiring the symbol at link time creates a problem. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org