emerge --update world failed on faac with an error: main.c:33:26: error: mp4v2/mp4v2.h: No such file or directory It seems because the dependency was pulled in in the wrong order. Doing emerge --update faac directly pulled in libmp4v2-1.9.1 to replace 1.5.0.1-r2 and it worked just fine. Version of faac being replaced was 1.28 oddly enough. I had just run a revdep-rebuild before this so it isn't something strange like that. I accidentally just fixed it without getting further info. Sorry, long night. Reproducible: Didn't try Expected Results: emerge --update world should've pulled in the same dependency order as emerge --update faac directly.
faac-1.28-r1 is the only version in portage and it has, RDEPEND=">=media-libs/libmp4v2-1.9.0" DEPEND="${RDEPEND}" which means mp4v2/mp4v2.h will be present both build and runtime. revdep-rebuild can't build pkgs in the right order, perhaps it's that?
either way, nothing left to fix
(In reply to comment #1) > faac-1.28-r1 is the only version in portage and it has, > > RDEPEND=">=media-libs/libmp4v2-1.9.0" > DEPEND="${RDEPEND}" > > which means mp4v2/mp4v2.h will be present both build ait wasn't revdep-rebuild which was building in the wrong order, it was emerge --update world. I am reopening this bug as I ran into the same thing now with python. Update world tries to update python withoutpulling in libffi, however emerge --update python properly pulls it in. Portage bug?nd runtime. > > revdep-rebuild can't build pkgs in the right order, perhaps it's that? >
Let me guess: 'emerge -upvD world' is OK ?
Please add emerge --info.
(In reply to comment #4) > Let me guess: 'emerge -upvD world' is OK ? > I wasn't able to keep it in a broken state as it was a production server, so keeping this bug open would probably do no good. Additionally, As I think about it, your guess may actually be right...
