RepoMirrors
/
mpv
mirror of https://github.com/mpv-player/mpv
1
0
Fork 0
Code Issues Releases Wiki Activity

3.0.x sux + some other stuff 

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@5002 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
gabucino 2002-03-09 14:09:27 +00:00
parent a3c426a712
commit ce3f36a3be
1 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
DOCS/gcc-2.96-3.0.html
View File

@ -69,9 +69,11 @@ because gcc <I>silently</I>, without any warning, ignored the whole asm block!
<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>
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>
@ -80,7 +82,7 @@ elements, including gcc 2.96 release number, enabled mplayer features, etc.
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
<B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>but</I> MPlayer !
</P>
<P>
@ -89,14 +91,14 @@ Also read <A HREF="users_against_developers.html">this</A> text !!!</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.
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
<B>Question:</B> No! You are wrong! Everything works with gcc 2.96 <I>including</I> MPlayer .
</P>
<P>
@ -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.
<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>
<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
<B>Answer:</B> Really? Are you sure? Ok. You know... here it is: ./configure --disable-gcc-checking
</P>
<P>
@ -122,10 +124,9 @@ It only means that you are lucky, until you find a problem. But don't forget the
</P>
<P>
<B>Answer:</B> It doesn't matter. Keep your commets for yourself. We're not interested in gcc 2.96 stories.
<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>