board.divers wrote: > Duncan Webb wrote: >> board.divers wrote: >> >>> Thanks for the info :D >>> >>> But now, I've try to compile pygoom2K4 >>> and i've got new problems :D >>> >>> [EMAIL PROTECTED]:~/Public/pygoom-2k4-0.1.0$ sudo python setup.py build >>> running build >>> running build_ext >>> building 'pygoom' extension >>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall >>> -Wstrict-prototypes -fPIC -I. -I./include -I/usr/include/goom/ >>> -I/usr/include/SDL/ -I/usr/include/python2.5/pygame/ >>> -I/usr/include/python2.5 -c src/cpudetect.c -o >>> build/temp.linux-i686-2.5/src/cpudetect.o -O9 -march=k8 -mtune=k8 -mmmx >>> -msse -fpic -fomit-frame-pointer -Wall >>> /tmp/ccaPCNKG.s: Assembler messages: >>> /tmp/ccaPCNKG.s:92: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:94: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:183: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:185: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:204: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:206: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:225: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:227: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:432: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:434: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:480: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:482: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:525: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:527: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:667: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:669: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:712: Error: bad register name `%rbx' >>> /tmp/ccaPCNKG.s:714: Error: bad register name `%rbx' >>> error: command 'gcc' failed with exit status 1 >>> >>> >>> The problem is probably due to to the cflags. >>> I've a amd duron processor (K8) so, I've just commented the pentium line >>> in the setup.py file. >>> >> It tells you to do this in the INSTALL read me. >> >> I really need to find a way to do this automatically. >> >> Duncan >> >> > Yes, but in the readme I just see "Fix the CFLAGS in setup.py" > and I've done that : > > ... > # includes > includes = ['.', > './include', > '/usr/include/goom/', > '/usr/include/SDL/', > '/usr/include/python2.5/pygame/', > ] > > # Intel P3 CFLAGS > #CFLAGS = ['-O9', '-march=pentium3', '-mtune=pentium3', '-mmmx', > '-msse', '-fno-pic', '-fomit-frame-pointer', '-Wall'] > # AMD 64 CFLAGS > CFLAGS = ['-O9', '-march=k8', '-mtune=k8', '-mmmx', '-msse', '-fpic', > '-fomit-frame-pointer', '-Wall'] > > # libraries > libdir = ['/usr/lib/' ] > ... > > I need to change something else ?
Try: Commenting out ARCH_X86_64 in the config file. if this doesn't work try using, k7 or k6 for march and mtune in setup.py's CFLAGS. What does gcc -v say about the target? If this still fails there should be a config.h in mplayer source directory, you can try copying this one on top of the supplied one. Duncan ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
