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

gcc 2.96... 

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@2443 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
arpi 2001-10-24 03:04:14 +00:00
parent 2324cfb6c8
commit 8b32cf14e5
1 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
configure vendored
View File

@ -449,14 +449,9 @@ if test "$cc_verc_fail" ; then
cat <<EOF
Please downgrade(upgrade) gcc compiler to gcc-2.95.2+ or gcc-3.0+ version!
Note: gcc 2.96 is RedHat's UNOFFICIAL (it can be found only on RedHat sites, or
in RedHat-based distributions) and BUGGY gcc release. gcc 2.96 is TOTALLY
unsupported by us, because it simply SKIPS or badly compiles some MMX codes!
Important: this is NOT an MPlayer-specific problem, numerous other projects
(DRI, avifile, etc..) have problems with this shit too. DO NOT USE gcc 2.96 !!!
If you don't want to downgrade, use the --disable-gcc-checking option to avoid
this check, but DO NOT SEND BUGREPORTS OR COMPLAIN, it's *YOUR* fault!
Get ready for mysterious crashes, no-picture bugs, strange noises... REALLY!
Note: gcc 2.96 is RedHat's UNOFFICIAL (it can be found only in RedHat,
Mandrake sites or distributions) and BUGGY gcc release. gcc 2.96 is TOTALLY
UNSUPPORTED by us. *** For details please read DOCS/gcc-2.96-3.0.html ***
EOF
die "Bad gcc version"
fi
@ -466,7 +461,11 @@ else
cat <<EOF
Hmm. You want to compile MPlayer with gcc 2.96? Ok. You know. Do it.
Hmm. You really want to compile MPlayer with gcc 2.96? Ok. You know. Do it.
But did you already read DOCS/gcc-2.96-3.0.html ???
*** BUT WE DO NOT RECOMMEND SENDING ANY MAIL TO THE ***
*** MAILING LISTS OR DIRECTLY TO THE AUTHORS! ***
@ -474,16 +473,19 @@ Hmm. You want to compile MPlayer with gcc 2.96? Ok. You know. Do it.
*** gcc 2.96 is broken. nobody will help you! ***
If you have any problem, then install 2.95.x or 3.0 version and try again.
If the problem still exists, then read DOCS/bugreports.html.
If the problem _still_ exists, then read DOCS/bugreports.html.
DO NOT SEND BUGREPORTS OR COMPLAIN, it's *YOUR* fault! (exactly gcc 2.96's)
Get ready for mysterious crashes, no-picture bugs, strange noises... REALLY!
EOF
echo -n "Enter keyword to continue: "
read _answer
if test "$_answer" != "gcc 2.96 is broken" ; then
die "Wrong answer. Next time try 'gcc 2.96 is broken'. But you'd better to downgrade."
fi
# if test "$_answer" != "gcc 2.96 is broken" ; then
# die "Wrong answer. Next time try 'gcc 2.96 is broken'. But you'd better to downgrade."
# fi
fi
# ---