Summary: | after emul-linux update mplayer-bin does not find libs anymore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Volker Hemmann <volkerarmin> |
Component: | [OLD] Library | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | peper, vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Volker Hemmann
2007-01-09 00:51:56 UTC
You should also update to app-emulation/emul-linux-x86-medialibs-1.2-r1 and app-emulation/emul-linux-x86-soundlibs-2.5-r2. Reopen If you still have problems after update. Hi, I updated them to the versions you said, now I get: /opt/mplayer-bin/bin/mplayer-bin: error while loading shared libraries: libSDL-1.2.so.0: cannot open shared object file: No such file or directory LD_LIBRARY_PATH=/emul/linux/x86/usr/lib32/ mplayer-bin path/to/file works around it. Then you need also emul-linux-x86-sdl-2.3-r1. yeah, but it sucks, that suddenly I have to update (at least) three different packages. One day everything works fine, next day everything falls apart. Which of the updates 'devided' the emul packages? And why did not all got updated, if it is needed anyway? all of the leaf nodes force the latest inner nodes I am not sure, that I do understand you correctly, but are you trying to tell me, that some update, that forced some of the emul-packages to become updated, broke mplayer-bin? But why? I mean, if there is an update, that might break stuff, why not updating everything, instead of leaving a half working mess? app-emulation/emul-linux-x86-compat-1.0-r2 app-admin/chrpath-0.13 app-emulation/emul-linux-x86-baselibs-2.5.5-r3 app-emulation/emul-linux-x86-xlibs-7.0-r8 app-emulation/emul-linux-x86-qtlibs-3.4.4-r4 app-emulation/emul-linux-x86-gtklibs-2.10.6.3-r3 media-video/realplayer-10.0.8-r1 was the update that broke mplayer-bin for me. Why do 'I' have to emerge some more updates by hand? From my point of view, portage only did half the job. It updated some packages, but not everything needed which resulted in breakage. Wait, that is worse than doing half the job. Portage only updated 'some' libs, when it should have updated everything. But why? Btw, I just looked at the realplayer ebuild. It demands some version of the emul packages installed, but there was no need for emul-updates. Which confuses me even more. So I had a partial emul-package update, that was not needed by the following package to work, which broke mplayer-bin. And that is not a bug? *sigh* I am sounding like an asshole - and I really don't want to. I should really get some sleep. But could somebody please explain, why I got in that mess? You are mixing ~amd64 and amd64 or didn't do emerge -uD world. But you are right that emul pkgs transition from /emul to /lib32 should have been done smoother. Thanks, I don't mix, I am purely ~amd64. yes, I should react more relaxed when problems apear. And yes, I did not a --deep update. In the past, I suffered regularly annoying problems after --deep updates, so I don't do it, if not told otherwise. |