Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to install Mplayer on my machine from the rpms on the website. I downloaded them, but when I try to install it says I am missing the libxvidcore.so.4 dependency. So, I downloaded the xvidcore tar file from xvid.org and installed it... but the mplayer rpms still fail out on the dependency.
The point here isn't really to get mplayer installed as fast as possible. I understand I can probably do it faster by installing from source or using yum. But, as a novice linux user, I want to understand how to fix these problems without running from them. I did search the forums and the FAQs and everything I found said to either do it from source or from yum. Can anyone explain the problem here and maybe point me in the right direction?
I want to install Mplayer on my machine from the rpms on the website. I downloaded them, but when I try to install it says I am missing the libxvidcore.so.4 dependency. So, I downloaded the xvidcore tar file from xvid.org and installed it... but the mplayer rpms still fail out on the dependency.
When installing libraries under Linux, you need to run a command called 'ldconfig'. Provided that the libraries are installed under one of the directories contained in /etc/ld.so.conf, all should be sweet after that.
ldconfig updates the library cache that is used by the run time linker.
Now, having said that, the rpm dependancy check will still fail if you haven't got the libxvid*.rpm package installed. The reason for this is that rpm can only find items in your package database. If you install from source, then you have bypassed rpm and it won't know what is going on. The best option is to find the libxvid*.rpm and install that. Alternatively, you can also use the '--nodeps' flag when installing the mplayer rpm.
Quote:
Originally Posted by MALDATA
But, as a novice linux user, I want to understand how to fix these problems without running from them.
everything I found said to either do it from source or from yum
That is your answer, do it from Yum. Package managers are fantastic, they really truly are. Use them whenever possible and you'l run into significantly less deps issues.
rkelsen: Sounds good, I'll give that a try and drop a message in here reporting sweet sweet victory or crushing defeat.
cs-cam: I've still got some research to do on yum. I know the basics but there's a lot about the repos and whatnot I need to figure out still. Basically, if it's not in the default repos, I do it from source or rpm. I agree that they're fantastic, but I think I learn better starting the hard way...
Now, having said that, the rpm dependancy check will still fail if you haven't got the libxvid*.rpm package installed. The reason for this is that rpm can only find items in your package database.
I didn't know that. Do other package managers work the same way, or is that something specific to rpms?
Distribution: PCLinuxOS 2007 on my laptop and Suse 10.2 on my desktop.
Posts: 341
Rep:
Quote:
Originally Posted by rkelsen
When installing libraries under Linux, you need to run a command called 'ldconfig'. Provided that the libraries are installed under one of the directories contained in /etc/ld.so.conf, all should be sweet after that.
ldconfig updates the library cache that is used by the run time linker.
Anyway, on the Xine documentation site, it tells me to install the xine-lib files first with the commands:
./configure
make install
which I did. It then says:
Make sure your /etc/ld.so.conf contains /usr/local/lib and continue with...
This is what you refer to in the quote above isn't it rkelsen? Well if i look at the file (directory?) /etc/ld.so.conf I can only find one called /etc/ld.so.conf.d and this appears to be empty. I have tried everything I can to get Xine installed, (read my thread above)and would really appreciate it if you could explain about the /etc/ld.so.conf bit.
Thanks.
I didn't know that. Do other package managers work the same way, or is that something specific to rpms?
If you install anything from source (using ./configure && make && make install) then there is an extremely high probability that your package manager won't see it. Some package managers are designed to work with source code, but even they won't see the items installed in such a manner.
Quote:
Originally Posted by Adrian Baker
After days wondering about this I just realised that /etc/ld.so.conf is a file whereas /etc/ld.so.conf.d is a directory.
My /etc/ld.so.conf DOES contain usr/local/lib
Good. Remember that once you've installed a library, you need to run the "ldconfig" command.
Now, from your other thread:
Quote:
Originally Posted by Adrian Baker
I tried
./configure --prefix=/usr/src/packages/BUILD/xine-lib-1.1.1/bin
You shouldn't need to use the --prefix option at all. By default, most source code is pre-configured to install itself under /usr/local. If you wanted to change that to another directory (say /opt) then you would use "--prefix=/opt".
Using the --prefix option in the manner you've tried is insane, and pretty much guaranteed to not work.
If you want to put the files under "/usr/src/packages/BUILD" so that you can make an rpm package yourself, you should use these 3 commands:
Code:
# ./configure
# make
# make install DESTDIR=/usr/src/packages/BUILD/xine-lib-1.1.1
But I don't know how to make an rpm package, so you'll have to read up on that yourself. Just be aware that the files installed to /usr/src/packages/BUILD will not be visible to the system. You'd have to make the rpm package and then install it in order for everything to work.
Yep, got it down. The only problem was that I ended up with an error like "cannot restore segment prot after reloc: Permission denied." I googled it and all I had to do was turn off SELinux to fix it, but I imagine I also could've fixed it without turning it off completely.
Distribution: PCLinuxOS 2007 on my laptop and Suse 10.2 on my desktop.
Posts: 341
Rep:
Hi rkelsen
Thanks so much for your help. After week of trying to get Xine to work I have finally got there!! I tried many different sources and finally installed it through Yast. However, the codecs failed to install and this has been a continual problem. However, I have configured Xine to use codecs that I have installed elsewhere and now it all works. I now can play DVDs through mplayer or Xine!
I finally feel that i at last have a working (basic) knowledge of Linux... yippee!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.