diff --git a/DOCS/users_against_developers.html b/DOCS/users_against_developers.html index 19fa09ab38..3f9103fffd 100644 --- a/DOCS/users_against_developers.html +++ b/DOCS/users_against_developers.html @@ -34,12 +34,10 @@ issued an official response to GCC 2.96. Many developers around the world began having problems with GCC 2.96, and started recommending other compilers. Examples are - Apache, MySQL, avifile and Wine. Other interesting links are - Real time Linux, Linux kernel news flash about kernel 2.4.17 and Voy Forum. @@ -49,7 +47,7 @@ bugs, especially since some workarounds may imply a performance penalty.

You can read about the other side of the story - at this site. + at this site. GCC 2.96 does not allow | (pipe) characters in assembler comments because it supports Intel as well as AT&T Syntax and the | character is a symbol in the Intel variant. The problem is that it silently ignores the @@ -63,25 +61,26 @@ If you want to compile with 2.96 give the --disable-gcc-checking flag to configure. Remember that you are on your own and do not report any bugs. 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.

+ we have had more than enough flame wars over GCC 2.96. Please let the matter + rest.

If you have problems with GCC 2.96, you can get 2.96-85 packages from the Red Hat ftp server, or just go for the 3.0.4 packages offered for version 7.2 and later. You can also get - gcc-3.1 packages - (unofficial, but working fine) 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:

+ gcc-3.2-10 packages + (unofficial, but working fine) and you can install them along the GCC 2.96 you + already have. MPlayer will detect it and use 3.2-10 instead of 2.96. If you do + not want to or cannot use the binary packages, here is how you can compile the + latest GCC from source:

  1. Go to the GCC mirrors page - page and download gcc-core-3.1.tar.gz. This includes the - complete C compiler and is sufficient for MPlayer. If you also want - C++, Java or some of the other advanced GCC features - gcc-3.1.tar.gz may better suit your needs.
    2. + page and download gcc-core-XXX.tar.gz where XXX is + the version number. This includes the complete C compiler and is sufficient + for MPlayer. If you also want C++, Java or some of the other advanced GCC + features gcc-XXX.tar.gz may better suit your needs.
  2. Extract the archive with
    - tar -xvzf gcc-core-3.1.tar.gz
    3. + tar -xvzf gcc-core-XXX.tar.gz
  3. 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
    @@ -89,7 +88,7 @@
  4. Then you can proceed to configure GCC in the build directory, but you need the configure from the source directory:
    cd gcc-build
    - ../gcc-3.1/configure
    5. + ../gcc-XXX/configure
  5. Compile GCC by issuing this command in the build directory:
    make bootstrap
  6. Now you can install GCC (as root) by typing
    @@ -121,8 +120,8 @@ mplayer-users about problems related to these closed-source drivers and their poor quality, instability and poor user and expert support. - Here is an example from the - + Some examples can be found on the + nVidia Linux Forum. Many of these problems/issues keep appearing repeatedly. We have been contacted by nVidia lately, and they said these bugs