Hello, After emerging libfam 2.7, I noticed that libfam library is now called libfam.0 and not libfam.so.0. That means that kde 3.1 refuses to start (it seeks libfam.so.0). A simple ln -s libfam.0.0.0 libfam.so.0 resolves the problem. I checked the forums, it seems I am not the only one to have this problem... Reproducible: Always Steps to Reproduce: 1. Emerge fam 2.7.0 2. Try to start kde (or licq, or anything that needs libfam) Actual Results: libfam.so.0 not found (I am putting this as "major". Sorry if it's to severe...)
Great! Another libtool bug. Just what We Need.
fixed in cvs
*** Bug 41078 has been marked as a duplicate of this bug. ***