diff --git a/DOCS/users_against_developers.html b/DOCS/users_against_developers.html index 7b5fa264d5..9638a4d976 100644 --- a/DOCS/users_against_developers.html +++ b/DOCS/users_against_developers.html @@ -25,15 +25,14 @@ mailing list. Number one is of course the topic of the
The background : there were/are the GCC 2.95 series. The best of them was 2.95.3 . Please note the style of the version numbering. This is how the GCC team numbers their compilers. The 2.95 series are good. -We never ever saw anything that was miscompiled because of the 2.95's faultiness.
+We never ever saw anything that was miscompiled because of the 2.95.3's faultiness.The action : RedHat started to include a GCC version of 2.96 with their distributions. Note the version numbering. This should be the GCC team's versioning. They patched the CVS version of GCC (something between 2.95 and 3.0) They patched it very deep, and used this version in the distrib because 3.0 wasn't out at time, and they wanted IA64 support ASAP (business reasons). -Oh, and GCC 2.95 miscompiles bash on the s390 architecture (there is -no RedHat distribution for s390..) .
+Oh, and GCC 2.95 miscompiles bash on the s390 architecture...The facts : MPlayer's compile process needs the
--disable-gcc-checking to proceed upon detecting a GCC version of
@@ -151,6 +150,12 @@ most likely be blacklisted.
We will (at least we wish) solve 2 of these problems in the next major release: +the legal problems (we're on removing all non-GPL codes and getting others to +change license to GPL) and the runtime CPU detection. Anyway, dependency on +various libraries, versions and environment parameters will remain.
+ +NVidia
We don't like nvidia's binary drives, their quality, unstability,