[MPlayer-dev-eng] impossible build mplayer revision 26320

[Reimar Döffinger]

On Thu, Apr 03, 2008 at 04:40:47PM +0100, Zé wrote:
> impossible build mplayer revision 26320, the configure options i use:
> 
> configuration: --prefix=/usr --datadir=/usr/share/mplayer --confdir=/etc/mplayer --libdir=/usr/lib64 --enable-largefiles --enable-freetype --enable-nas --disable-sighandler --enable-gui --language=all --disable-faad-internal --enable-lirc --enable-tv --enable-joystick --enable-gl --disable-svga --enable-directfb --enable-mencoder --disable-vesa --enable-theora --enable-menu --enable-smb --xanimcodecsdir=/usr/X11R6/lib/xanim/mods --realcodecsdir=/usr/lib64/RealPlayer10GOLD/codecs --codecsdir=/usr/lib/win32 --with-extraincdir=/usr/include/lzo --enable-fribidi --enable-zr --enable-xvmc
> 
> 
> and the output error:
> 
> In file included from ../libavutil/common.h:85,
>                  from ../libavutil/avutil.h:52,
>                  from ../libavcodec/avcodec.h:30,
>                  from jpeg_enc.c:35:
> ../libavutil/internal.h:118:1: warning: "memcpy" redefined
> In file included from /usr/include/string.h:428,
>                  from ../libavutil/common.h:37,
>                  from ../libavutil/avutil.h:52,
>                  from ../libavcodec/avcodec.h:30,
>                  from jpeg_enc.c:35:
> /usr/include/bits/string3.h:43:1: warning: this is the location of the 
> previous definition
> jpeg_enc.c: In function ‘jpeg_enc_init’:
> jpeg_enc.c:304: error: ‘I_TYPE’ undeclared (first use in this 
> function)
> jpeg_enc.c:304: error: (Each undeclared identifier is reported only once
> jpeg_enc.c:304: error: for each function it appears in.)
> make[1]: ** [jpeg_enc.o] Erro 1
> make[1]: Saindo do diretório 
> `/mnt/ext3/linux/rpm_build_tree/BUILD/mplayer/libvo'
> make: ** [libvo/libvo.a] Erro 2
> erro: Código de saída inválido do /home/mmodem/rpm/tmp/rpm-tmp.70202 (%build)
> 
> im also attaching configure.log so that theres no doubts.

This is the wrong list for bug reports, they belong on -users.
And this particular problem has been fixed in SVN r26322.
I have no idea if the code still works though, you will have to test it.
And if there are bugs, report them on -users or via bugzilla, otherwise
I will ignore them.