Mercurial > mplayer.hg

--- a/DOCS/documentation.html	Thu Jun 27 13:00:40 2002 +0000
+++ b/DOCS/documentation.html	Thu Jun 27 16:17:54 2002 +0000
@@ -417,28 +417,27 @@
 <UL>
   <LI><B>binutils</B> - suggested version is <B>2.11.x</B> . This program is
     responsible for generating MMX/3DNow!/etc instructions, thus very important.</LI>
-  <LI><B>gcc</B> - suggested version is from <B>2.95.3</B> to <B>2.95.4</B>.
-    <B>NEVER</B> use 2.96 or 3.x.x !!! They generate faulty code. If you decide
-    to change gcc from 2.96, then don't decide in favor of 3.x just because
-    it's newer! In some ways it's even worse than 2.96. So downgrade to
-    2.95.x (downgrade libstdc++ too, other programs may need it) or don't
-    up/downgrade at all (but in this case, be prepared for compiletime/runtime
-    problems).
-    If you vote for 3.x.x, try to use the latest version, early releases had
-    various bugs, so be sure you use at least 3.1, it's tested and working.
-    Don't use RedHat's gcc 3.x versions! 3.0.4-RH reproducably dies with
-    internal error during GUI compilation (vanilla 3.0.4 does not).
-    Detailed information about gcc 2.96's bugs (that are still NOT fixed, they
-    are WORKAROUNDED in <B>MPlayer</B>!) can be found
+  <LI><B>gcc</B> - suggested versions are: <B>2.95.3</B>, <B>2.95.4</B> and <B>3.1</B>.
+    <B>NEVER</B> use 2.96 or 3.0.x !!! They generate faulty code for MPlayer.
+    If you decide to change gcc from 2.96, then don't decide in favor of 3.0.x
+    just because it's newer! Early releases of 3.0.x were even more buggy than
+    2.96. So downgrade to 2.95.x (downgrade libstdc++ too, other programs may
+    need it) or don't up/downgrade at all (but in this case, be prepared for
+    runtime problems). If you vote for 3.x.x, try to use the latest version,
+    early releases had various bugs, so be sure you use at least 3.1, it's
+    tested and working. Don't use RedHat's gcc 3.0.x versions! 3.0.4-RH
+    reproducibly dies with internal error during GUI compilation (vanilla 3.0.4
+    does not). Detailed information about gcc 2.96's bugs (that are still NOT
+    fixed, they have been WORKED AROUND in <B>MPlayer</B>!) can be found
     <A HREF="users_against_developers.html"><B><I>here</I></B></A> and in the
     <A HREF="faq.html">FAQ</A> !</LI>
   <LI><B>XFree86</B> - suggested version is <B>always the newest (4.2.0)</B>.
-    Normally everyone wants this, as starting from XFree86 4.0.2, it contains
-    the <A HREF="video.html#2.3.1.2">XVideo</A> extension (somewhere referred
+    Normally, everyone wants this, as starting with XFree86 4.0.2, it contains
+    the <A HREF="video.html#2.3.1.2">XVideo</A> extension (somewhere referred to
     as <B>Xv</B>) which is needed to enable the hardware YUV acceleration (fast
     image display) on cards that support it. <A HREF="video.html#2.3.1.2">More
     information available.</A><BR>
-    Make sure its <B>development package</B> is installed too otherwise
+    Make sure its <B>development package</B> is installed, too, otherwise
     it won't work.<BR>
     For some videocards you don't need XFree86. See list below.</LI>
   <LI><B>make</B> - suggested version is <B>always the newest</B> (at least 3.79.x). This
@@ -450,6 +449,8 @@
     Useful for both <B>MPlayer</B> and <B>MEncoder</B> if you plan to work with jpeg files.</LI>
   <LI><B>libpng</B> - recommended and default (M)PNG decoder. Required for GUI.
     Useful for both <B>MPlayer</B> and <B>MEncoder</B>.</LI>
+  <LI><B>lame</B> - recommended, needed for encoding MP3 audio with MEncoder,
+    suggested version is <B>always the newest</B> (at least 3.90).</LI>
   <LI><B>libogg</B> - optional, needed for playing OGG file format.</LI>
   <LI><B>libvorbis</B> - optional, needed for playing OGG Vorbis audio.</LI>
 </UL>
@@ -2510,10 +2511,10 @@
   Workaround: ./configure --disable-sse etc. options</LI>

 <LI>"Internal buffer inconsistency" during MEncoder run:<BR>
-  Problem: known problem when lame was compiled with gcc 2.96 or 3.x, no fix
-  yet.<BR>
-  Workaround: compile lame with gcc 2.95. Be sure to remove any installed
-  lame packages, they may have been compiled with gcc 2.96 .</LI>
+  Problem: known problem when lame &lt; 3.90 was compiled with gcc 2.96 or 3.x.<BR>
+  Solution: use lame &gt;=3.90.<BR>
+  Workaround: compile lame with gcc 2.95.x and remove any already installed
+  lame packages, they may have been compiled with gcc 2.96.</LI>

 <LI>Messed up MP2/MP3 sound on PPC:<BR>
   Problem: known GCC miscompilation bug on PPC platforms, no fix yet.<BR>
--- a/DOCS/users_against_developers.html	Thu Jun 27 13:00:40 2002 +0000
+++ b/DOCS/users_against_developers.html	Thu Jun 27 16:17:54 2002 +0000
@@ -65,17 +65,21 @@

 <P>If you have problems with GCC 2.96, you can get 2.96-85 packages from the
 Red Hat <A HREF="ftp://updates.redhat.com">ftp server</A>, or just go for the
-3.04 packages offered for version 7.2 and later. If you do not want to or cannot
-use the binary packages, here is how you can compile GCC 3.0.4 from source:</P>
+3.0.4 packages offered for version 7.2 and later. You can also get gcc-3.1
+packages (unofficial, but working fine)
+<A HREF="ftp://people.redhat.com/jakub/gcc3/3.1-1/">here</A> and you can
+install them along the gcc-2.96 you already have. MPlayer will detect it and
+use 3.1 instead of 2.96. If you do not want to or cannot use the binary
+packages, here is how you can compile GCC 3.1 from source:</P>

 <UL>
   <LI>Go to the <A HREF="http://gcc.gnu.org/mirrors.html">GCC mirrors page</A>
-    page and download <CODE>gcc-core-3.0.4.tar.gz</CODE>.  This includes the
+    page and download <CODE>gcc-core-3.1.tar.gz</CODE>.  This includes the
     complete C compiler and is sufficient for <B>MPlayer</B>. If you also want
     C++, Java or some of the other advanced GCC features
-    <CODE>gcc-3.0.4.tar.gz</CODE> may better suit your needs.</LI>
+    <CODE>gcc-3.1.tar.gz</CODE> may better suit your needs.</LI>
   <LI>Extract the archive with<BR>
-    <CODE>tar -xvzf gcc-core-3.0.4.tar.gz</CODE></LI>
+    <CODE>tar -xvzf gcc-core-3.1.tar.gz</CODE></LI>
   <LI>GCC is not built inside the source directory itself like most programs,
     but needs a build directory outside the source directory.  Thus you need to
     create this directory via<BR>
@@ -83,7 +87,7 @@
   <LI>Then you can proceed to configure gcc in the build directory, but you need
     the configure from the source directory:<BR>
     <CODE>cd gcc-build<BR>
-    ../gcc-3.0.4/configure</CODE></LI>
+    ../gcc-3.1/configure</CODE></LI>
   <LI>Compile GCC by issuing this command in the build directory:<BR>
     <CODE>make bootstrap</CODE></LI>
   <LI>Now you can install GCC (as root) by typing<BR>