You are not logged in.
Pages: 1
I've recently installed mplayer on my system.
Pacman installed libftdi and lirc-utils as dependencies but when I tried to start mplayer i got:
mplayer: error while loading shared libraries: libx264.so.112: cannot open shared object file: No such file or directory
I fixed this installing x264 too, so shouldn't this package be somewhere in the dependency tree of mplayer??
Sorry if I have been silly.
Last edited by DarioP (2011-01-19 21:20:21)
Offline
x264 already is a dependency of mplayer.
Offline
Yes.. so is reported in the package page of mplayer, but trust me, I have just had a fresh install and I had to manual install x264.
Something didn't work.
Offline
is simple, pacman -Qs x264. if you have other name of that package then is your problem.
or you installed mplayer with pacman -Sy mplayer, which is wrong
Last edited by wonder (2011-01-19 21:41:11)
Give what you have. To someone, it may be better than you dare to think.
Offline
I installed mplayer with pacman -S mplayer and it installed some dependencies too.
Then I had to do pacman -S x264 as this required package wasn't installed by the previous command.
That's all. I don't know what happened, I've never had this kind of problem before.
I'm just reporting my experience, if it's useless let it drop
Last edited by DarioP (2011-01-19 22:24:53)
Offline
maybe the mirror was out of sync and didn't have the new x264
Offline
The chance of pacman not picking up a dependency (when installing stuff correctly) is absolutely minimal. I'm pretty sure your mirror being out of date (or syncing at the moment you updated) is the problem. Grep your logs for x264, I'm willing to bet your 'install' was actually an upgrade.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Grep your logs for x264
I'll be glad to do it if you tell me how.. where are packages logs stored?
Offline
/var/log/pacman.log
Offline
I am not sure if my problem is related to yours, but I got the same error message yesterday, concerning the exact same library (libx264.so.112), except I was trying to run a fresh install of ffmpeg.
Before I installed ffmpeg, I ran pacman Sy to update the package list. When I got that error after the install, I checked in /usr/lib/, and sure enough, I had libx264.so.107.
I had read somewhere that mplayer often uses older libraries than ffmpeg, and that, if ffmpeg is installed after mplayer, ffmpeg will not add some of the newer libraries. In addition, my version of mplayer was about one month old.
So, I did a complete purge of mplayer and ffmpeg:
pacman -Rs ffmpeg smplayer mplayer
Then, I installed ffmpeg again:
'pacman -S ffmpeg
After ffmpeg, I installed mplayer:
pacman -S mplayer
Now, my libx264.so is version 112, and both ffmpeg and mplayer work fine. (I didn't reinstall smplayer -- the CLI version is fine).
Offline
If you don't want problems like this, don't do
pacman -Sy
pacman -S pkg
or
pacman -Sy pkg
If you don't understand why, read the documentation/wiki. When using any rolling release there will be library upgrades, and new programs will be linked against those, not the old libraries.
https://wiki.archlinux.org/index.php/Pa … g_packages
pacman -Syu
pacman -S pkg
or
pacman -Syu pkg
or just installing without syncing the database (but it might fail if the package has been upgraded and deps can't be found):
pacman -S pkg
will all work fine.
Last edited by thestinger (2011-01-20 18:19:54)
Offline
Thanks for the tip on using the sysupgrade flag ("u") with the refresh flag ("y"). I assume that "-Suy" does the exact same thing as "-Syu" -- the package list is always refreshed prior to the sysupgrade, which is finally followed by installing the new package.
However, I did not want to upgrade my entire system; I just wanted ffmpeg and mplayer to run. If my solution had not worked, then I probably would have tried a sysupgrade. I actually had to do that once before.
I am aware of problems with linking out-of-date dependencies in some rolling release distros, but I have also read about the peculiar relationship between mplayer and ffmpeg, and that sometimes it is best to install ffmpeg prior to mplayer.
Offline
As pointed out times and again partial upgrades - and those involve also installing one package after syncing your database - is asking for trouble. Either you do a full upgrade, or you don't do it at all. That's how it works.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
doesn't matter because our mplayer doesn't use system ffmpeg.
Give what you have. To someone, it may be better than you dare to think.
Offline
The chance of pacman not picking up a dependency (when installing stuff correctly) is absolutely minimal. I'm pretty sure your mirror being out of date (or syncing at the moment you updated) is the problem. Grep your logs for x264, I'm willing to bet your 'install' was actually an upgrade.
You were right!
$ cat /var/log/pacman.log | grep x264
[2011-01-03 19:05] installed x264 (20101013-1)
[2011-01-19 22:11] Running 'pacman -S x264'
[2011-01-19 22:11] upgraded x264 (20101013-1 -> 20110115-1)
I probably have had a partial update during that couple of week, so thanks for the clarification
Offline
Pages: 1