comparison DOCS/gcc-2.96-3.0.html @ 5001:b4c4d1abb7a4

3.0.x sux + some other stuff

5000:bb20ff7aa21d

</P>

<P>
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. <B>Only 2.96 is broken</B>, but it depends on many environment
elements, including gcc 2.96 release number, enabled mplayer features, etc.
<I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone.</I>
</P>

<P><B>Answer 2:</B></P>

<P>
Also read <A HREF="users_against_developers.html">this</A> text !!!</P>

<P>
<B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>but</I> MPlayer
</P>

<P>
<B>Answer:</B>
</P>

<P>
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.
</P>

<P>
<B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>including</I> MPlayer
</P>

<P>
<B>Answer:</B>
</P>

Good. Be happy. But you must know, it depends on many environment
elements, including gcc 2.96 release number, enabled mplayer features, etc.
<I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone!</I>
It only means that you are lucky, until you find a problem. But don't forget the
<B>No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96</B>

<P>
<B>Question:</B> Ok. Understood. But I want to give it a try... how to compile with gcc 2.96?
</P>

<P>
<B>Answer:</B> Really? Are you sure? Ok. You know... here is it: ./configure --disable-gcc-checking
</P>

<P>
<B>Question:</B> No! I don't agree with you, because ...
</P>

<P>
<B>Answer:</B> It doesn't matter. Keep your commets for yourself. We're not interested in gcc 2.96 stories.
</P>


</FONT>
</BODY>
</HTML>

5001:b4c4d1abb7a4

</P>

<P>
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 2.95.3 (<B>MEncoder</B> won't work with 2.95.2 because it miscompiles
some MMX instructions). <B>2.96 and 3.0.x are broken</B>, but it depends on
many environment elements, including gcc 2.96 release number, enabled mplayer
features, etc. <I>If it works for you using gcc 2.96, it doesn't mean it will
work for everyone.</I>
</P>

<P><B>Answer 2:</B></P>

<P>
Also read <A HREF="users_against_developers.html">this</A> text !!!</P>

<P>
<B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>but</I> MPlayer !
</P>

<P>
<B>Answer:</B>
</P>

<P>
No. You are wrong!
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.
</P>

<P>
<B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>including</I> MPlayer .
</P>

<P>
<B>Answer:</B>
</P>

Good. Be happy. But you must know, it depends on many environment
elements, including gcc 2.96 release number, enabled mplayer features, etc.
<I>If it works for you using gcc 2.96, it doesn't mean it will work for everyone!</I>
It only means that you are lucky, until you find a problem. But don't forget the
<B>No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96</B> !

<P>
<B>Question:</B> Ok. Understood. But I want to give it a try... how to compile with gcc 2.96?
</P>

<P>
<B>Answer:</B> Really? Are you sure? Ok. You know... here it is: ./configure --disable-gcc-checking
</P>

<P>
<B>Question:</B> No! I don't agree with you, because ...
</P>

<P>
<B>Answer:</B> It doesn't matter. Keep your comments to yourself. We're not interested in gcc 2.96 stories.
</P>

</FONT>
</BODY>
</HTML>