Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Oh,shit - I am lost.Last time I tried mplayer rpm (just for kicks) it was one rpm.
Go with the source - Yoda is right.
All you need to do is get the source,unpack it,cd to the directory and do ./configure (with gui ./configure --enable-gui) ,make and make install.
At least you'll get some errormsgs. that make sense when something goes wrong with the ./configure step.
Right ... Gone through a fairly long and tortuous process here, so bear with me please ... =)
Downloaded the mplayer source and unpacked it ... On configure, it tells me that I have GCC 2.96 (which apparently sucks) and that I should up/downgrade. So; I downloaded the GCC3.1.1 source, unpacked it, configure | make bootstrap (i think it was?) | make install ... All done successfully ...
However, when I go to configure mplayer again, it tells me that I still have version 2.96 installed. I assume that this is because its installed in a different directory and its still looking at the old one ... I've done a little digging and discovered that I probably need to set the path environment variable to the new GCC location (?). I've also read that it would be better to do this with a switch on the /configure (like --classpath) ...
Does anyone happen to know the syntax for this? Also consider that I can't find the gcc executable in the build directory (or subdirs) anywhere ... Although I'm pretty sure it built successfully, so it's probably just my lame searching skills.
Good job on getting GCC installed. I would have taken the RPM's from your mandrake disc (and yes, you should install all the related rpm's for it as well) for GCC 3 and used those. Yes, it does install along side, it, not replacing your older one. when you type ./configure you can follow that with --help so:
will reveal MANY options for you to use during the configure process of mplayer.
So, first you'll want to see what gcc3.1.1 got installed to. SO:
should produce some ideas on that for you. If not, the readme or install info in the source you d/l would probably let you know.
So, then you'll need to specify it during configure like this:
./configure --cc=COMPILER (where COMPILER is replaced with the path to your UPDATED CC/GCC compiler. So say it was installed to /usr/bin/gcc-3.1.1, then you'd replace COPILER with /usr/bin/gcc-3.1.1)
OR you could make the symlink gcc point to your new GCC compiler with:
enter root password
ln -sf /usr/bin/gcc-3.1.1 /usr/bin/gcc
IF the location of your new gcc is /usr/bin/gcc-3.1.1; IF NOT replace that portion of the example with the correct location.
Some other things to specify during the configure:
./configure --cc=COMPILER --enable-gui
Ok, I've found the new gcc executable in /usr/local/bin and pointed the configuration at it ... its halted again (on the GTK check, again, no less) ... I know I have GTK installed (I even have GTK+2 or something like that - damned if I know how to get anything to recognise it's there! =P) - as I mentioned previously, GTK-Gnut built with no problems ... Possibly an error in mplayers config script?
sorry to see that you're having such a hard time with MPEGs, Aphix. Normally this is where I would have given up. It's encouraging for me to see other people stuggling with Linux because then I know I'm not the only one who has to go through crap like this.
Well you win32 looks good, my assumption was you had it in a subfolder there...
Give the divx a go, and anytime now would be a good time to start reading the mail postings over on mplayer's website. You might even want to post if you can't figure it out, after reading read the docs of course.
That, or send Acid_Kewpie a small email pointing him to this thread, as he is pretty much our resident MPlayer expert
First post here - Google invited me in, hope that's okay.
I have the same problem as the gentleman who started this thread (the Blue Screen of Irritation on playing back mpegs).
I was just wondering if it was ever resolved. I normally get sound but that's all. This applies to several applications including gtv and mplayer. However, mpeg_play provides me with video but no sound.
Yes - I am currently playing my mpegs in two seperate applications!!! I try to start both applications within the same second and this works, but I think you'll agree it's not ideal .
I assume because of the multiple app nature of the problem, there is some common library they use that is mesbehaving on my system which was once SuSE 7.2 (but has been chewed a bit).
I am C++ person so I've got the technical knowledge, but not much familiarity with how Linux is put together.
Doesn't the fact that the same problem occurs with diverse apps (gtv, mplayer, XMovie, ...) imply that there is something more fundamental here, or do these apps actually share these codecs? How do they do that?