Problem compiling transcode.

Steve Campbell goondennews at
Sun Jul 27 02:11:16 PDT 2003

I am not sure if this is the best place to ask, especially since my LFS has 
been in place for over a year now, so it's fairly long in the tooth, and by 
rights needs a good upgrading.

Anyway, having gone gently mental in windows trying to convert video files 
to vcd's, I thought it was about time I used Linux to do it, however, when 
I try to install tanscode ( needed by just about all video conversion 
programs), I get the following symptoms.....
it configure's perfectly ( no options passed to config) 
but a few seconds into make it exit's thusly....

ake[2]: Entering directory `/mnt/test/downloads/transcode-0.6.8/aclib'
source='cputest.c' object='cputest.o' libtool=no \
depfile='.deps/cputest.Po' tmpdepfile='.deps/cputest.TPo' \
depmode=gcc /bin/sh ../autotools/depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I..     -funroll-loops -ffast-math -DLINUX 
-I/usr/X11R6/include -O3 -fomit-frame-pointer -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c `test -f 'cputest.c' || 
echo './'`cputest.c
/usr/local/bin/nasm -felf -g -o memcpy.o memcpy.s
memcpy.s:197: parser: instruction expected
memcpy.s:198: symbol `movdqa' redefined
memcpy.s:198: parser: instruction expected
memcpy.s:199: symbol `movdqa' redefined
memcpy.s:199: parser: instruction expected
memcpy.s:200: symbol `movdqa' redefined
memcpy.s:200: parser: instruction expected
memcpy.s:202: parser: instruction expected
memcpy.s:203: symbol `movntdq' redefined
memcpy.s:203: parser: instruction expected
memcpy.s:204: symbol `movntdq' redefined
memcpy.s:204: parser: instruction expected
memcpy.s:205: symbol `movntdq' redefined
memcpy.s:205: parser: instruction expected
make[2]: *** [memcpy.o] Error 1
make[2]: Leaving directory `/mnt/test/downloads/transcode-0.6.8/aclib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/test/downloads/transcode-0.6.8'
make: *** [all] Error 2

Can anyone enlighten me as to ahy, and what I may be able to do about it?
To me it looks like something has gotten up nasm's nose rather than gcc.

Please note, that I am the proof that you don't need to be a programmer to 
use Linux, so anything more complex than ./configure && make && make 
install gives me a headache :)

registered Linux user #212154
Don't get mad, get Linux

More information about the blfs-support mailing list