aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
Diffstat
-rw-r--r--DOCS/bugreports.html62
-rw-r--r--DOCS/faq.html13
-rw-r--r--DOCS/users_against_developers.html44
3 files changed, 67 insertions, 52 deletions
diff --git a/DOCS/bugreports.html b/DOCS/bugreports.html
index 0e9ec3d07c..67453797be 100644
--- a/DOCS/bugreports.html
+++ b/DOCS/bugreports.html
@@ -50,21 +50,27 @@ and do not forget to include this valuable information:</P>
<UL>
<LI>Your Linux distribution or operating system e.g.:
<UL>
- <LI>Red Hat 7.1
- <LI>Slackware 7.0 + devel packs from 7.1 ...
+ <LI>Red Hat 7.1</LI>
+ <LI>Slackware 7.0 + devel packs from 7.1 ...</LI>
</UL>
+</LI>
<LI>kernel version:<BR>
- <CODE>uname -a</CODE>
+ <CODE>uname -a</CODE></LI>
<LI>libc version:<BR>
- <CODE>ls -l /lib/libc[.-]*</CODE>
+ <CODE>ls -l /lib/libc[.-]*</CODE></LI>
<LI>X version:<BR>
- <CODE>X -version</CODE>
+ <CODE>X -version</CODE></LI>
<LI>gcc and ld versions:<BR>
<CODE>gcc -v<BR>
- ld -v</CODE>
+ ld -v</CODE></LI>
<LI>binutils version:<BR>
- <CODE>as --version</CODE>
-<LI>if only the GUI is buggy :
+ <CODE>as --version</CODE></LI>
+<LI>If you have problems with fullscreen mode:
+ <UL>
+ <LI>Window manager type and version</LI>
+ </UL>
+</LI>
+<LI>If only the GUI is buggy:
<UL>
<LI>GTK version</LI>
<LI>GLIB version</LI>
@@ -78,35 +84,39 @@ and do not forget to include this valuable information:</P>
<UL>
<LI>CPU info (this works on Linux only):<BR>
- <CODE>cat /proc/cpuinfo</CODE>
-<LI>Video card manufacturer and model, e.g.:<BR>
+ <CODE>cat /proc/cpuinfo</CODE></LI>
+<LI>Video card manufacturer and model, e.g.:
<UL>
- <LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM
- <LI>Matrox G400 DH 32MB SGRAM
+ <LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</LI>
+ <LI>Matrox G400 DH 32MB SGRAM</LI>
</UL>
-<LI>Video driver type &amp; version, e.g.:<BR>
+</LI>
+<LI>Video driver type &amp; version, e.g.:
<UL>
- <LI>X built-in driver
- <LI>nVidia 0.9.623
- <LI>Utah-GLX CVS 2001-02-17
- <LI>DRI from X 4.0.3
+ <LI>X built-in driver</LI>
+ <LI>nVidia 0.9.623</LI>
+ <LI>Utah-GLX CVS 2001-02-17</LI>
+ <LI>DRI from X 4.0.3</LI>
</UL>
-<LI>Sound card type &amp; driver, e.g.:<BR>
+</LI>
+<LI>Sound card type &amp; driver, e.g.:
<UL>
- <LI>Creative SBLive! Gold with OSS driver from oss.creative.com
- <LI>Creative SB16 with kernel OSS drivers
- <LI>GUS PnP with ALSA OSS emulation
+ <LI>Creative SBLive! Gold with OSS driver from oss.creative.com</LI>
+ <LI>Creative SB16 with kernel OSS drivers</LI>
+ <LI>GUS PnP with ALSA OSS emulation</LI>
</UL>
-<LI>if in doubt include <CODE>lspci -vv</CODE> output on Linux systems
+</LI>
+<LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI>
</UL>
<P><B>For compilation problems/errors</B></P>
<P><B><I>Please include these files:</I></B></P>
-<UL><LI>configure.log
-<LI>config.h
-<LI>config.mak
-<LI>libvo/config.mak
+<UL>
+ <LI>configure.log</LI>
+ <LI>config.h</LI>
+ <LI>config.mak</LI>
+ <LI>libvo/config.mak</LI>
</UL>
<P><B>For playback problems</B></P>
diff --git a/DOCS/faq.html b/DOCS/faq.html
index 656ca3df3f..6fc8bc8894 100644
--- a/DOCS/faq.html
+++ b/DOCS/faq.html
@@ -37,7 +37,7 @@ Probably there is no such file or directory.
What's the problem with gcc 2.96?
</B></TD><TR><TD></TD><TD VALIGN=top><FONT CLASS="text">A:</TD><TD><FONT CLASS="text">
<B><I>We strongly discourage the use of gcc 2.96!!!</I></B><BR>
-Read <A HREF="gcc-2.96-3.0.html">this</A> and <A HREF="users_against_developers.html">this</A>
+Read <A HREF="users_against_developers.html#gcc">this</A>
document for details. If you still really really want to use it, be sure to get
the latest release, but remember that you are on your own. Do <B>not</B> report
bugs or ask for help on the mailing lists. We will <B>not</B> provide any support
@@ -49,7 +49,7 @@ in case you run into problems.
Great, I have gcc 3.0.1 from Red Hat/Mandrake, then I'm fine--!
</B></TD><TR><TD></TD><TD VALIGN=top><FONT CLASS="text">A:</TD><TD><FONT CLASS="text">
No, since there have been/are issues with these compilers as well.<BR>
-Use the 2.95.x series for reliability (not <A HREF="gcc-2.96-3.0.html">2.96</A>).
+Use the 2.95.x series for reliability (not <A HREF="users_against_developers.html#gcc">2.96</A>).
Use the latest gcc 3.0.x (starting at 3.0.2) if you want to use a 3.0.x version.
</TD><TR><TD COLSPAN=3>&nbsp;</TD><TR>
@@ -110,7 +110,7 @@ big house, etc etc. Do you really want it? It seems.</P>
<TD></TD><TD VALIGN=top><FONT CLASS="text">Q:</TD><TD WIDTH=100%><B><FONT CLASS="text">
Where can I find information about gcc 2.96 bugs?
</B></TD><TR><TD></TD><TD VALIGN=top><FONT CLASS="text">A:</TD><TD><FONT CLASS="text">
-In <A HREF="gcc-2.96-3.0.html">this</A> document. And <A HREF="users_against_developers.html">this</A>
+<A HREF="users_against_developers.html#gcc">This</A>
document describes why Red Hat released 2.96 and other interesting things.
</TD><TR><TD COLSPAN=3>&nbsp;</TD><TR>
@@ -441,7 +441,8 @@ use <B>MPlayer</B> on a CPU different from the one it was compiled on.
<TD></TD><TD VALIGN=top><FONT CLASS="text">Q:</TD><TD WIDTH=100%><B><FONT CLASS="text">
I have problems with [your window manager] and fullscreen xv/xmga/sdl/x11 modes ...
</B></TD><TR><TD></TD><TD VALIGN=top><FONT CLASS="text">A:</TD><TD><FONT CLASS="text">
-Use the <CODE>-fsmode</CODE> switch. See example.conf or the man page.
+Read the <A HREF="bugreports.html">bug reporting guidelines</A> and send us a
+proper bug report.
</TD><TR><TD COLSPAN=3>&nbsp;</TD><TR>
<TD></TD><TD VALIGN=top><FONT CLASS="text">Q:</TD><TD WIDTH=100%><B><FONT CLASS="text">
@@ -690,7 +691,7 @@ It's for your information only but our criteria are:
Speed:<BR>
This parameter can be computed easily:
<OL>
- <LI>Which movies do you plan to watch?</LI>
+ <LI>Which movies do you plan to watch?
<UL>
<LI><B>MPEG1:</B> 320x200@32=256000<BR>
You need only 256*25fps=6.4MB/sec of bandwidth (This format can be played
@@ -708,6 +709,7 @@ This parameter can be computed easily:
32MB of video memory to watch this stream: 16MB for the RGB area and 16MB
for the YUV area.</LI>
</UL>
+ </LI>
<LI>The bandwidth of PCI slots is: 33MHz*32Bit=133MB/sec. PCI2.1 has
66MHz*32Bit=266MB/sec which is more than enough for playing any movie (except
HDTV streams which really require an AGP bus).</LI>
@@ -717,6 +719,7 @@ This parameter can be computed easily:
<LI><B>DIMM</B> - Good if your video card has 128-bit memory access.</LI>
<LI><B>DDR</B> - Is fast enough for all types.</LI>
</UL>
+ </LI>
</OL>
Note: DGA comparison shows that there is no visible difference between video
cards which have the same type of video memory installed.<BR>
diff --git a/DOCS/users_against_developers.html b/DOCS/users_against_developers.html
index b6fd20fe1d..3e7886fad7 100644
--- a/DOCS/users_against_developers.html
+++ b/DOCS/users_against_developers.html
@@ -66,29 +66,31 @@ flag to configure. Remember that you are on your own and <B>do not report any
bugs</B>. If you do, you will only get banned from our mailing list because
we have had more than enough flame wars over GCC 2.96. Please let the matter rest.</P>
-<P>If you have problems with GCC 2.96, here is how you can get GCC 3.0.4 to work
-(submitted by <A HREF="mailto:willis_matthew@yahoo.com">Matt Willis</A>):</P>
+<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>
<UL>
- <LI>Go to the
- <A HREF="http://gcc.gnu.org/mirrors.html">GCC mirrors page</A>
- page and download the following (you may not need everything):<BR>
- <CODE>gcc-g++-3.0.4.tar.gz<BR>
- gcc-objc-3.0.4.tar.gz<BR>
- gcc-3.0.4.tar.gz<BR>
- gcc-g77-3.0.4.tar.gz<BR>
- gcc-testsuite-3.0.4.tar.gz<BR>
- gcc-core-3.0.4.tar.gz<BR>
- gcc-java-3.0.4.tar.gz</CODE>
- </LI>
- <LI>Unpack the files, make a build directory, and build:<BR>
- <CODE>tar -xvzf gcc-*3.0.4.tar.gz<BR>
- mkdir gcc-build<BR>
- cd gcc-build<BR>
- ../gcc-3.0.4/configure --prefix=/opt --program-suffix=-3.0.4<BR>
- make bootstrap; mkdir -p /opt; make install</CODE></LI>
- <LI>Set your path to include <CODE>/opt/bin</CODE><BR>
- <CODE>export PATH=/opt/bin:${PATH}</CODE></LI>
+ <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
+ 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>
+ <LI>Extract the archive with<BR>
+ <CODE>tar -xvzf gcc-core-3.0.4.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>
+ <CODE>mkdir gcc-build</CODE></LI>
+ <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>
+ <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>
+ <CODE>make install</CODE></LI>
</UL>
<P><A NAME=binary><B>Binary distribution of MPlayer</B></A></P>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-03 09:31:24 +0000