Building MPlayer 1.0-pre6a under YDL-4.0 [LONG]

[Joseph E. Sacco, Ph.D.]

Not to worry... Matthias Saou has posted a working version of MPlayer on
freshrpms.net. If you use yum to pull it down, yum will handle the
dependencies.

-Joseph

=========================================================
On Sat, 2005-01-08 at 08:04, Albrecht Dreß wrote:
> Am 07.01.05 13:20 schrieb(en) Matthias Saou:
> > Thanks for sharing all this information!
> > It seems that for me, on a stock YDL4 system, the only required change
> > was
> > the one in uio.h. Attached is a unified diff that does the exact same
> > change as the patch you posted.
> 
> I attached the patch, but the compiler still crashes when trying to build  
> MPlayer:
> 
> <snip>
> cc -c -I../libvo -I../../libvo -I/usr/X11R6/include -O3 -mcpu=7450  
> -fsigned-char -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64    
> -I. -I..  -I.. -o yuv2rgb_altivec.o yuv2rgb_altivec.c
> yuv2rgb_altivec.c: In function `altivec_yuv2packedX':
> yuv2rgb_altivec.c:796: warning: assignment from incompatible pointer type
> yuv2rgb_altivec.c:803: warning: assignment from incompatible pointer type
> yuv2rgb_altivec.c: In function `cvtyuvtoRGB':
> yuv2rgb_altivec.c:247: error: unrecognizable insn:
> (insn:HI 5 4 6 0 (nil) (set (reg/v:V8HI 120 [ U ])
>          (mem/f:V8HI (plus:SI (reg/f:SI 67 ap)
>                  (const_int 8 [0x8])) [9 U+0 S16 A128])) -1 (nil)
>      (nil))
> yuv2rgb_altivec.c:247: internal compiler error: in extract_insn, at  
> recog.c:2175
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:https://bugs.terrasoftsolutions.com/bugzilla> for instructions.
> Preprocessed source stored into /tmp/ccOxBtg4.out file, please attach this  
> to your bugreport.
> make[1]: *** [yuv2rgb_altivec.o] Error 1
> make[1]: Leaving directory `/home/albrecht/Neues/MPlayer-1.0pre6a/postproc'
> make: *** [postproc/libswscale.a] Error 2
> </snip>
> 
> Is this a problem of the semi-broken gcc coming with YDL 4? As gcc 3.3.3  
> is not the latest available, I guess it doesn't make sense to pass this  
> report to the gcc people. Will there be a gcc upgrade available, or to  
> which gcc version (3.4.2?) should I upgrade manually?
> 
> Tia,
> Cheers,
> 
> Albrecht.
-- 
joseph_sacco[at]comcast[dot]net