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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I installed mplayer through source codes on my Slackware 12. At my first install I didn't notice that libmp3lame wasn't installed and so I could not use mencoder to extract audio from movies to form .mp3 files. I installed lame through source codes.
On configuring mplayer, mplayer didn't detect it. I found this webpage:
Here it is written that lame must be configure with --prefix=/usr or else mplayer won't detect it. When I tried this out, mplayer detected lame and now I have mencoder working.
Why is this so? Suppose I install lame in an arbitrary directory (eg: /softwares). I add /softwares/lib to my ld.so.con and run ldconfig -v. libmp3lame.so shows up. Is there any configure option in mplayer to make it detect lame in /softwares?
By default, lame sets everything up in /usr/local. Whereas, I'm assuming, mplayer looks for libraries to link against in /usr (or any directory defined in ld.so.con). /usr/local may not be listed in ld.so.con.
If you add /software to ld.so.con, it should work.
Did you install mplayer before or after you installed lame?
I don't know a whole hell of a lot about linking, unfortunately.
It makes sense to install everything to a single dir - I used to use /opt - and I don't know why I stopped doing it. Regardless, the only logical thing I can think of, is that if you installed mplayer before lame, it wouldn't find it due to the fact that mplayer was probably built without support for libmp3lame because the library did not exist.
I first installed lame in /softwares. I then installed mplayer which didn't find it. So I installed lame in /usr. On configuring mplayer, this time lame was detected.
The link I provided explicitly says that if lame is configured without --prefix=/usr, mplayer may not detect it. Why so? This would be a problem for people who would want to install all softwares in a different directory (in my case /software and in you case /opt). I tried out mplayer configure options like --toolamelibdir=/compilations etc but none worked.
If it is a deficiency in the ./configure file of mplayer, would it be possible to do some surgery to it and change the path where it looks for lame.h? I am not all that comfortable with scripts, but I'll give it a try soon.