[MPlayer-users] Error compiling SVN Revision: 23304

[Reimar Doeffinger]

Hello,
On Mon, May 14, 2007 at 12:30:14AM -0600, Jeremy Hansen wrote:
> I am getting the same error as before...
> 
> Same error as above
> 
> make[1]: Entering directory `/home/jbhansen/program-downloads/mplayer/loader'
> cc -DMPLAYER -D__WINE__ -DNOAVIFILE_HEADERS -I../libavcodec
> -I../libavformat -Wdeclaration-after-statement -I. -I.. -I../libavutil
> -W -Wall -Wno-unused-parameter -O2 -march=pentium-m -mtune=pentium-m
> -g3  -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE64_SOURCE -I/usr/X11/include -I/usr/include/
> -I/usr/include/SDL  -D_REENTRANT -I/opt/kde/include/artsc -pthread
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> -I/usr/include/freetype2 -I/usr/local/include -I/usr/include/gtk-2.0
> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/freetype2
> -I/usr/X11R6/include -I/usr/include/libpng12   -I/usr/local/include
> -I/usr/local/include/dvdnav -fno-omit-frame-pointer
> -mno-omit-leaf-frame-pointer   -c -o ldt_keeper.o ldt_keeper.c
> - Hide quoted text -
> ldt_keeper.c: In function `Setup_LDT_Keeper':
> ldt_keeper.c:194: error: storage size of 'array' isn't known
> ldt_keeper.c:226: error: invalid application of `sizeof' to incomplete
> type `user_desc'
> ldt_keeper.c:194: warning: unused variable `array'
> make[1]: *** [ldt_keeper.o] Error 1
> make[1]: Leaving directory `/home/jbhansen/program-downloads/mplayer/loader'
> make: *** [loader/libloader.a] Error 2

As explained in some previous thread your kernel headers are
incompatible with MPlayer. Unless they are fixed you can not use the
win32 codecs, you must configure with --disable-win32dll
(if you report this as bug to your distro they might say that this is
intended and that they do not want architecture-specific code in the
headers in /usr/include - in that case win32 codecs just won't be
supported by MPlayer, though we might consider adding a check that will
automatically disable this feature.)

Greetings,
Reimar Doeffinger