[MPlayer-users] mplayer compilation error

[David C. Diemer]

Dean,

1. It was a mistype about gcc 3.4. I misread my information.

2. To try something out, I uninstalled mplayer, downloaded the pre10 RPMs 
(common, mplayer, gui, & fonts) and tried it out. It worked okay except that 
the video and the audio refused to sync right no matter what settings I 
tried. I uninstalled those and went back to the pre9 and it worked just 
fine. Go figure. After removing pre9 again, I installed all the pre10 RPMS 
again(!). Then I decided to try the source RPM(!), tune, and compile from 
there. Voila!  All my video/sync problems went away.

3. As for flaming, what I meant was that I didn't want others to assume that 
I was an RPM or .tgz bigot and I didn't want grief for mixing the two!

So you may be asking yourself, "What the hell does that have to do with my 
problem?"  Well, the straight RPM installation worked -- badly -- but it 
worked. Have you tried just RPMs and seen how it worked? I assume you have 
and went on to customize like I did but it's worth asking.

Finally, what previous releases have you tried compiling?


Dave



----Original Message Follows----
From: "Dean S. Messing" <deanm at sharplabs.com>
Reply-To: mplayer-users at mplayerhq.hu
To: mplayer-users at mplayerhq.hu
Subject: Re: [MPlayer-users] mplayer compilation error
Date: Tue, 26 Nov 2002 10:24:01 -0800 (PST)

[Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]

David C. Diemer writes:
  :: Dean,
  ::
  :: I gathered from reviewing your posts that you downloaded the source RPM
  :: and compiled from there. I've tried other source RPMs but then why I
  :: would want an RPM that has the source in it when it's available as a
  :: '.tgz' file?

The reason I want the .src.rpm is so that I can build an .rpm (a
binary package).  This, then, gets installed and my system rpm
'registry' gets updated with all the requirements, dependencies, and
things that the package provides to the system at large.

There are _many_ advantages to running an "all .rpm" system
on which I can wax eloquent in private mail if you like.

  :: Have you tried to download and extract the source RPM again into a new
  :: directory (file writing error or download error? It only takes one bit
  :: to be off!) and compiling again?

Yes.  Corey Hickey also brought this up on Friday.
Please see my post:

http://www.mplayerhq.hu/pipermail/mplayer-users/2002-November/024396.html

At the end of the post I do an explicit diff between the .tar.bz2 present
in the .src.rpm and the .tgz on the Mplayer site (after unpacking, of 
course).
The compare bit for bit.

  :: You could also try downloading, extracting, and compiling the '.tgz'.
  :: It _shouldn't_ be any different than the source RPM but I've had 
nothing
  :: but good experiences with the '.tgz'. Now before I get flamed on this
  :: suggestion, I KNOW the source RPM shouldn't be different than the 
'.tgz'
  :: BUT...

That's what I did in the post I mention.  Why should I flame you?
Your suggestions are what I would suggest myself.

I only wish that someone (one of the mplayer wizards) would chime in
here and tell me what to do.  Surely someone with an Athlon-mp (or
xp?), running stock Mdk 9.0 (gcc 3.2) can try configuring and
compiling with the switches I mention and see if they get the error.

They can even use the .tgz from the site if they like.  It isn't going
to make any difference.  If they get this same error then maybe this
will get the attention of the "higher powers".

Dean

_______________________________________________
RTFM!!!  http://www.MPlayerHQ.hu/DOCS
Search:  http://www.MPlayerHQ.hu/cgi-bin/htsearch
http://mplayerhq.hu/mailman/listinfo/mplayer-users


_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus