On Wed, 11 Sep 2002, John Richard Smith wrote: > No I just took the old lame lame-20020408cvs-1mdk. off and put > the lame-encoder-3.92-3tex.i586.rpm on ,using the usual commands, > went to mplyayer , encoded a chapter , then played it back in the usual > way.
Ok, this answers my question... at least I know it doesn't ;-) Don't worry, I will try it myself in about 30 minutes. Talking about CVS versions, I cannot compile the CVS versions of Lame from 2 days ago. Mine is also a month or 2 old, and although there probably haven't been that many changes, I descided to test it out for my mencoder-dvd->divx-manual. But I can't compile :-( It keeps bombing out here when it comes to compiling the "frontend", which turns out to be the lame binary itself. If I choose --without-frontend, it compiles fine but only installs the libs and so on, but no actualy lame binary itself :-( I know mencoder would probably work with this, but that's not the point I think... at least if someone is going to have the lame installed, they should be able to use it too separately. John, would you mind just trying to ./configure and make a fresh downloaded version? No need to install it though, as my question is purely based of the fact that I want to know if it's the CVS version or my computer where the error lies. If it compiles and creates a "lame" executable, I know it's me ;-) Thanks Greetings Ralph -- Homepage: http://tuxpower.f2g.net/
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
