Dear Users,
 
I have trouble with the mjpegtools-1.6.1 's compilation.

Please see this report :

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/local/include -DG_LOG_DOMAIN=\"lavtools\" 
-DLAVPLAY_VERSION=\"1.6.1\" -I/usr/include 
-I/usr/src/RPM/BUILD/mjpegtools-1.6.1/usr/include -I/usr/include/glib-1.2 
-I/usr/lib/glib/include -I/usr/local/include -I 
/usr/src/RPM/BUILD/mjpegtools-1.6.1/quicktime4linux -I/usr/X11R6/include -I 
/usr/X11R6/include -I../utils -I/usr/local/include/avifile -I/usr/include/gtk-1.2 
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include 
-I/usr/src/RPM/BUILD/mjpegtools-1.6.1/jpeg-mmx -mcpu=i686 -march=i686 -O3 
-fomit-frame-pointer -pipe -mcpu=pentiumpro -march=i586 -ffast-math 
-fno-strength-reduce -Wall -Wunused -c lav_io.c -MT lav_io.lo -MD -MP -MF 
.deps/lav_io.TPlo  -fPIC -DPIC -o .libs/lav_io.lo
cc1: warning: changing search order for system directory "/usr/local/include"
cc1: warning:   as it has already been specified as a non-system directory
cc1: warning: changing search order for system directory "/usr/include"
cc1: warning:   as it has already been specified as a non-system directory
lav_io.c: In function `lav_open_input_file':
lav_io.c:1148: `QUICKTIME_YUV420' undeclared (first use in this function)
lav_io.c:1148: (Each undeclared identifier is reported only once
lav_io.c:1148: for each function it appears in.)
make[2]: *** [lav_io.lo] Error 1
make[2]: Leaving directory `/usr/src/RPM/BUILD/mjpegtools-1.6.1/lavtools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/RPM/BUILD/mjpegtools-1.6.1'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.89829 (%build)


thanks in advance
Aurélien Grosshans


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to