Other gcc 3.x problems comes from broken libstdc++ or glibc header (std_*.h) installation. They are not our fault. MPlayer compiles and works well with -gcc 3.x versions. Only 2.96 is broken, but it depends on many environment -elements, including gcc 2.96 release number, enabled mplayer features, etc. -If it works for you using gcc 2.96, it doesn't mean it will work for everyone. +gcc 2.95.3 (MEncoder won't work with 2.95.2 because it miscompiles +some MMX instructions). 2.96 and 3.0.x are broken, but it depends on +many environment elements, including gcc 2.96 release number, enabled mplayer +features, etc. If it works for you using gcc 2.96, it doesn't mean it will +work for everyone.
Answer 2:
@@ -80,7 +82,7 @@ elements, including gcc 2.96 release number, enabled mplayer features, etc. Also read this text !!!-Question: No! You are wrong! Everything works with gcc 2.96 but MPlayer +Question: No! You are wrong! Everything works with gcc 2.96 but MPlayer !
@@ -89,14 +91,14 @@ Also read this text !!!
No. You are wrong! -Several projects (mainly which source contains high optimized inline asm code) -had problems with gcc 2.96. For example: avifile, MESA / DRI, Wine, ffmpeg, lame, NuppelVideo. -But other projects already workarounded gcc bugs (changed code which -triggered compiler bugs) so they work for now. +Several projects (mostly which contain highly optimized inline asm code) +had problems with gcc 2.96. For example: avifile, MESA / DRI, Wine, ffmpeg, +lame, NuppelVideo, MySQL. But other projects already workarounded gcc bugs +(changed code which triggered compiler bugs) so they work for now.
-Question: No! You are wrong! Everything works with gcc 2.96 including MPlayer +Question: No! You are wrong! Everything works with gcc 2.96 including MPlayer .
@@ -107,14 +109,14 @@ Good. Be happy. But you must know, it depends on many environment elements, including gcc 2.96 release number, enabled mplayer features, etc. If it works for you using gcc 2.96, it doesn't mean it will work for everyone! It only means that you are lucky, until you find a problem. But don't forget the -No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96 +No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96 !
Question: Ok. Understood. But I want to give it a try... how to compile with gcc 2.96?
-Answer: Really? Are you sure? Ok. You know... here is it: ./configure --disable-gcc-checking +Answer: Really? Are you sure? Ok. You know... here it is: ./configure --disable-gcc-checking
@@ -122,10 +124,9 @@ It only means that you are lucky, until you find a problem. But don't forget the
-Answer: It doesn't matter. Keep your commets for yourself. We're not interested in gcc 2.96 stories. +Answer: It doesn't matter. Keep your comments to yourself. We're not interested in gcc 2.96 stories.
-