libmad compile issue on amd64

Compiling cvs I get:

cc -c -pipe  -Wall -W  -O2 -fPIC  -DOPIE_NO_DEBUG -DOPIE_NO_BUILTIN_SHUTDOWN 
-DUSE_FILE_NOTIFICATION -DOPIE_SOUND_FRAGMENT_SHIFT=16 -DFPM_INTEL 
-DQT_NO_DEBUG -I/home/cmorgan/opie/mkspecs/qws/linux-generic-g++ -I. 
-I/home/cmorgan/opie/include -I.. 
-I/home/cmorgan/axim_downloads/qt-2.3.10/include -I.moc/x86-linux/ 
-o .obj/x86-linux/synth.o synth.c
{standard input}: Assembler messages:
{standard input}:636: Error: Incorrect register `%r9' used with `l' suffix
{standard input}:643: Error: Incorrect register `%r11' used with `l' suffix
{standard input}:647: Error: Incorrect register `%r10' used with `l' suffix
{standard input}:648: Error: Incorrect register `%rax' used with `l' suffix
...snip lots of lines here...
{standard input}:2851: Error: Incorrect register `%rax' used with `l' suffix
{standard input}:2857: Error: Incorrect register `%rax' used with `l' suffix
{standard input}:2863: Error: Incorrect register `%rax' used with `l' suffix
make[1]: *** [.obj/x86-linux/synth.o] Error 1
make[1]: Leaving directory 
`/home/cmorgan/opie/core/multimedia/opieplayer/libmad'
make: *** [core/multimedia/opieplayer/libmad] Error 2
~/opie$

Mad 0.15.1b compiles correctly.  A diff of mad.h between mad 0.15.1b and 
opie's mad reveals a bunch of changes, some that look specifically to address 
the issue of compiling on 64bit platforms.  What is the policy on updating 
the mad library in opie?  Are these libraries taken directly from mad?  
Should I be sending in a patch that implements whatever 64bit fixes mainline 
mad code made or looking to patch up to 0.15.1b?

Chris
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel