Relevant part of build log: /bin/grep: /usr/lib/libogg.la: No such file or directory /bin/sed: can't read /usr/lib/libogg.la: No such file or directory libtool: link: `/usr/lib/libogg.la' is not a valid libtool archive make[5]: *** [libtheora_plugin.la] Error 1 make[5]: *** Waiting for unfinished jobs.... This file does indeed not exist on my system. ebuild media-libs/libogg-1.1.4 says at the end of the merge: * This version of libogg has stopped installing .la files. This may * cause compilation failures in other packages. To fix this problem, * install dev-util/lafilefixer and run: * lafilefixer --justfixit
Yep. Good thing you found the message, it includes everything I wanted to say :-)
(or revdep-rebuild)
(In reply to comment #1) > Yep. Good thing you found the message, it includes everything I wanted to say > :-) > Perhaps the VLC ebuild could give a little hint, too ... Btw. after running lafilefixer (which fixed ~1250 files on my system) it compiled fine.
(In reply to comment #3) > (In reply to comment #1) > > Yep. Good thing you found the message, it includes everything I wanted to say > > :-) > > > > Perhaps the VLC ebuild could give a little hint, too ... > > Btw. after running lafilefixer (which fixed ~1250 files on my system) it > compiled fine. > This error could have come even from a package that really doesn't use libogg on systems where LDFLAGS="-Wl,--as-needed" isn't used because libtool has a bad habit of inserting false (indirect) deps into .la files. There is absolutely no way of telling where it fails for "user a" and then for "user b", sorry. Just keep in mind next time you see a missing .la file it most likely needs a revdep-rebuild (slower way) or lafilefixer (faster way)
(In reply to comment #4) > This error could have come even from a package that really doesn't use libogg > on systems where LDFLAGS="-Wl,--as-needed" isn't used because libtool has a bad > habit of inserting false (indirect) deps into .la files. There is absolutely no > way of telling where it fails for "user a" and then for "user b", sorry. I see, thanks a lot for the explanation !
*** Bug 277454 has been marked as a duplicate of this bug. ***
