[MPlayer-users] mplayer can run on my arm926 board

[bytex]

I download the mplayer from the svn server(version 27418). 
 
and my config is:
 
 ./configure --cc=arm-linux-gcc --host-cc=gcc --target=arm-armv4l-linux \
--enable-cross-compile \
--enable-static \
--disable-win32dll \
--disable-dvdread --disable-dvdnav --disable-libdvdcss-internal \
--enable-fbdev \
--disable-mencoder \
--disable-live 
 
my cross compiler is arm-linux-gcc 3.4.1
 
No mistakes have occured during the compiling process.
 
Then I try to play a ts video with mplay on my arm926 board.
 
But I got the error message:

 
 MPlayer dev-SVN-r27418-3.4.1 (C) 2000-2008 MPlayer Team
CPU: ARM
Playing birds.ts.
TS file format detected.
VIDEO MPEG2(pid=34) AUDIO MPA(pid=33) NO SUBS (yet)!  PROGRAM N. 10
VIDEO:  MPEG2  720x576  (aspect 2)  25.000 fps  3372.0 kbps (421.5 kbyte/s)
==========================================================================
Opening video decoder: [mpegpes] MPEG 1/2 Video passthrough
VDec: vo config request - 720 x 576 (preferred colorspace: Mpeg PES)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
The selected video_out device is incompatible with this codec.
Try appending the scale filter to your filter list,
MPlayer interrupted by signal 4 in module: decode_video
- MPlayer crashed by an 'Illegal Instruction'.
  It usually happens when you run it on a CPU different than the one it was
  compiled/optimized for.mpeg2] vfm: ffmpeg (FFmpeg MPEG-2)
  Verify this!============================================================
- MPlayer crashed by bad usage of CPU/FPU/RAM.============================
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.mp3lib MPEG layer-2, layer-3)
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your===
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.
 
 
could anyone give me some advice？
 
 
Thanks.