From 5f72bb4caae5080f8d450dbb5e546340c398a685 Mon Sep 17 00:00:00 2001 From: diego Date: Tue, 27 Aug 2002 08:12:58 +0000 Subject: [PATCH] Settle for GCC, not gcc. 10l for telling Andras otherwise. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7095 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/users_against_developers.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/DOCS/users_against_developers.html b/DOCS/users_against_developers.html index 558a8ab34a..28136dd54b 100644 --- a/DOCS/users_against_developers.html +++ b/DOCS/users_against_developers.html @@ -21,7 +21,7 @@

The background: The GCC 2.95 series is an official GNU release and version 2.95.3 of GCC is the most bug-free in that series. - We have never noticed compilation problems that we could trace to gcc-2.95.3. + We have never noticed compilation problems that we could trace to GCC 2.95.3. Starting with Red Hat Linux 7.0, Red Hat included a heavily patched CVS version of GCC in their distribution and named it 2.96. Red Hat included this version in the distribution because GCC 3.0 was not finished @@ -70,7 +70,7 @@ 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 + 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:

@@ -86,7 +86,7 @@ but needs a build directory outside the source directory. Thus you need to create this directory via
mkdir gcc-build -
  • Then you can proceed to configure gcc in the build directory, but you need +
  • 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