On Thu, Oct 14, 2004 at 05:09:19PM +0200, Pander wrote: > Hi all, > > Building transcode for powerpc from source doesn't work. Can anyone tell > me how to build transcode with > debian on a powerpc? > > if gcc -DHAVE_CONFIG_H -I.. -I. -I.. -I. -Wall -fPIC -DPIC > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 > -fomit-frame-pointer -O3 -I../libmpeg2 -I./../libmpeg2 -MT cpu_accel.o > -MD -MP -MF ".deps/cpu_accel.Tpo" \ > -c -o cpu_accel.o `test -f 'cpu_accel.c' || echo './'`cpu_accel.c; \ > then mv -f ".deps/cpu_accel.Tpo" ".deps/cpu_accel.Po"; \ > else rm -f ".deps/cpu_accel.Tpo"; exit 1; \ > fi > /tmp/ccwbm0g4.s: Assembler messages: > /tmp/ccwbm0g4.s:185: Error: Unrecognized opcode: `vand' > make[2]: *** [cpu_accel.o] Error 1 > make[2]: Leaving directory `/tmp/transcode-0.6.12/libvo' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/transcode-0.6.12' > make: *** [all] Error 2 It's an altivec operation, the configure/Makefile is broken somewhere, explicitly disabling altivec (configure --disable-altivec) still tries to compile the altivec code. HAVE_PPC_ALTIVEC gets falsy defined. I don't know how to fix this though, I never really understood autoconf/automake. You can manually disable the define in config.h:220 to get it compiled for now. You should file a bug report afterwards. Johannes -- 3. The most fun you can have with your clothes on.
Attachment:
signature.asc
Description: Digital signature