On Wed, 8 Jan 2003 11:22:34 -0600 Tom Brinkman <[EMAIL PROTECTED]> wrote:
> Well, I suspect it's your ./config options, not gcc. MOF, I've > never need either --cc=/usr/bin/gcc-3.2 or 2>/root/Desktop/el1. > mplayer compiles just fine with Mandrakes gcc > 2.96. It even did then > as long as --disable-gcc-checking was used. I always need to check > the mplayer docs or run './configure --help' to figure out what > options to add, and there's a few that are documented yet. Yes, Mplayer works with gcc 2.96, but not efficiently. But that's not really the point, as John who was asking this needs / wants mencoder too, and mencoder skrews up badly with 0.96. I can't quite remember what the problem was with 0.96, but I do know that it's a documented bug, not only with mplayer, but in general. Why Mandrake and Redhat ever used it I don't actually know. Even under LM 8.2 I installed 3.x and removed 0.96 totally, and never had a problem. The reason why John uses the "2>/root/Desktop/el1" is to trace the output. I personally don't do this as while it's compiling I check the output myself. > IRRC, somethin like './configure --prefix=/usr --with win32 > something, --with qtx codecs something was what I used. 'Course > you'll need to check that syntax ;) ... and have the various libs and > codecs installed before you compile, otherwise mplayer won't find > 'em. I got tired of fooling with all the current config options and > now just use the rpms ;) Then too, the CVS isn't guaranteed to > compile, tho it usually does. Latest as of today is 20030108, so you > might wanna quit foolin with that old one you've got. IIRC, most of > the bugfixs in CVS are currently for DVD's and mencoder, but I don't > use either (so what'a I know ;) The CVS in general is pretty much always stable from my experience. Actually since about a year ago I only use the CVS. In between somewhere I tried some RPM's, but, although they worked, I didn't like the performance. Not too sure exactly what the problem was though, but configuring and installing myself has always been the best solution. There is a lot of documentation on mplayer, almost on every aspect, it just takes time to read it. These days, as 1 year ago I use mplayer / gmplayer (for the girlfriend) for video-playing, DVD's and of course mencoder to rip DVD's, producing excellent results with some cvs versions better than others, but on the whole excellent and twice as fast as when I used to have a dual-boot to windows. > One thing tho, if you tried, even unsuccesfully to compile > mplayer, then in the mplayer src dir, delete 'config.h' before you > try again. Also, I always run ./configure and make as user, only > su'ing to root for make install (as with all tarballs). Me too... I don't like to ./configure and "make" as root... never really liked it either as it's always in my normal user-directory, and deleting the source folder never works as files configured by root have to be deleted as root ;-) Just a hint to people trying to compile mencoder with lame support... build your own lame rpm's or just manually configure and compile it, as most of the ones I have tried miss something, and can't compile into mencoder. John just had this problem (private e-mails off the mailing list). I don't know where he got the rpm's from, but they did not work. I have encountered this problem many times from users mailing me asking how I rip DVD's, as they couldn't get lame support. Just another 5 cents (must beat least an euro now?!) :-) Greetings Ralph -- http://tuxpower.f2g.net/ http://axljab.homelinux.org:8080/ "I have opinions of my own, strong opinions, but I don't always agree with them." - George H. W. Bush
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
