Building mplayer-svn using internal ffmpeg-svn libraries [SOLVED]

Question

Yeah,
I know that a bunch of us are having errors building mplayer-svn against ffmpeg-svn internal libraries.
The error:
libvo/vo_yuv4mpeg.o: In function `flip_page':
vo_yuv4mpeg.c:(.text+0x694): undefined reference to `rgb24toyv12'
vo_yuv4mpeg.c:(.text+0x6f0): undefined reference to `rgb24toyv12'
vo_yuv4mpeg.c:(.text+0x848): undefined reference to `rgb24toyv12'
libmpcodecs/vf_palette.o: In function `put_image':
vf_palette.c:(.text+0x3ee): undefined reference to `palette8topacked32'
vf_palette.c:(.text+0x431): undefined reference to `palette8topacked24'
vf_palette.c:(.text+0x453): undefined reference to `palette8torgb16'
vf_palette.c:(.text+0x473): undefined reference to `palette8torgb15'
vf_palette.c:(.text+0x489): undefined reference to `palette8tobgr16'
vf_palette.c:(.text+0x4a1): undefined reference to `palette8tobgr15'
vf_palette.c:(.text+0x50a): undefined reference to `palette8topacked32'
vf_palette.c:(.text+0x55e): undefined reference to `palette8torgb15'
vf_palette.c:(.text+0x5b3): undefined reference to `palette8torgb16'
vf_palette.c:(.text+0x5d0): undefined reference to `palette8topacked24'
vf_palette.c:(.text+0x5ed): undefined reference to `palette8tobgr15'
vf_palette.c:(.text+0x60a): undefined reference to `palette8tobgr16'
libmpcodecs/vf_rgb2bgr.o: In function `put_image':
vf_rgb2bgr.c:(.text+0x1d7): undefined reference to `rgb24tobgr24'
vf_rgb2bgr.c:(.text+0x20a): undefined reference to `rgb32tobgr32'
vf_rgb2bgr.c:(.text+0x274): undefined reference to `rgb24tobgr24'
vf_rgb2bgr.c:(.text+0x290): undefined reference to `rgb32tobgr32'
libmpcodecs/vf_yuy2.o: In function `put_image':
vf_yuy2.c:(.text+0xf7): undefined reference to `yv12toyuy2'
vf_yuy2.c:(.text+0x154): undefined reference to `yuv422ptoyuy2'
collect2: ld returned 1 exit status
make: *** [mplayer] Error 1
All of this is coming from swscale. Enabling Mplayer's internal swscale fixes the build for me, but it's hardly a solution seeing that there is no difference at all in between the code bases.
The question:
Why are Archers seeing this and yet there's no traces that I can find anywhere on the web? I ask because I don't know if it's a Mplayer bug, a FFmpeg bug, or one of the core libraries in Arch? In short, I don't know who to file a bug report with.
What I know:
1) The build fails in different places on different architectures.
2) Mplayer seems to not be able to find yasm even though x264 and FFmpeg find it fine, even with the configure flag --yasm=YASM.
3) FFmpeg is not installing any swscale header file other than libswscale/swscale.h and force installing it does not help.
    a) There is no difference at all in the Makefile between the two code bases.

Answer 1

wonder wrote:to be fair i don't think you can build mplayer-svn against ffmpeg-svn. you can only with mplayer-mt-git against ffmpeg-mt-git or something like that.
I've been doing it daily for well over a year. Maybe even two.
-- Edit--
If anyone cares, it's because of how Mplayer deals with FFmpeg's header files. For instance, Mplayer is looking for yuv2rgb.h, but FFmpeg now produces yuv2rgb_mmx.h at runtime on my system. It looks as if libswscale's build files are being generated per architecture for usage of ASM code. Mplayer isn't looking at things quite right anymore.