media-libs/libmad-0.15.1b-r5 deletes libmad.la required by kde-base/kdelibs-3.5.9-r4 (with USE=mad) from the ebuild: src_install() { [SNIP] find "${D}" -name '*.la' -delete } Reproducible: Always Steps to Reproduce: 1. set USE=mad 2. emerge both packages Actual Results: kde-base/kdelibs-3.5.9-r4 fails while linking with the following message: grep: /usr/lib64/libmad.la: No such file or directory /bin/sed: can't read /usr/lib64/libmad.la: No such file or directory libtool: link: `/usr/lib64/libmad.la' is not a valid libtool archive
did you run revdep-rebuild ?
same with media-libs/libmad-0.15.1b-r4 on ~x86, here the following package fails to build: kde-base/kdeartwork-kscreensaver-3.5.9 (first to fail, I downgraded libmad upon this failure) USE(libmad)= USE(kscreensaver)=arts opengl kdeenablefinal xinerama
no revdep-rebuild, it happened while emerge -uaeDN world (after successful emerge -uaeDN system).
Run revdep-rebuild.
(In reply to comment #3) > This change also breaks basket-1.0.3.1, but downgrading libmad to -r4 fixes the > issue. Diego -- why the change to libmad to delete the .la files? If you can > help me understand the issue, maybe I can help with a solution. > Diego made changes to the libmad emerge that forcefully deletes the .la files on his own initiative. He posted information about it on his own blog - but doesn't cite libmad (making searching for it a bit of a problem). He may have some good points, but fails to actually let anyone know unless you're already following his blog and can read between the lines. UNFORTUNATELY revdep-rebuild does NOT fix this. It probably should, but that's for another bug. Other people (specifically Diego) have tried to offer this "solution" - but have obviously never tested it themselves. How to work around it? Re-emerge arts. That "fixes" the libmad issues (since it's from arts that the .la is being pulled in.
