I've seem to have run in to this problem on many distributions (except arch, only got it once), is that some library (liba) is linked to (libb). liba can't compile because it refers to libb.so.1, however, I do have a libb.so.2. Presumably a newer version of the libb object. Why is this? Is there a good reason to (not) do this? How do you prevent such things happening?
(first of all i´m very bad in english but i try it )
i think libX.so.2 has more code that can be loaded by a programm than
libX.so.1 so if one application is linked aggainst libX.so.1 it can´t handle the stuff in libX.so.2... arch is compiled against the newest library (or it should be)and i think redhat or suse-linux have a kind of binary compatibilty (every binary compiled for suse 8.1 should run on suse 9.1) i don´t think arch have this because arch use the newest and coolest stuff and compile every application which need library XYZ would be recompiled........