[Fwd: Re: [packman] transcode]

[Rainer Lay]

search in the config.log for your problem, i.e. mjpegtools/yuv4mpeg.h
In line 3619, you will find a message, that file mjpeg_types.h could not
be found. On my i386 machine, it is installed at
/usr/include/mjpegtools/mjpeg_types.h

Can you please check this?

kind regards,
Rainer

Peter Czanik schrieb:
> Hello,
> Wanted to send to the rest of you, not just Henne... And also a URL with
> complete config.log is available at
> http://www.mkk.szie.hu/~czanik/transcode.config.log
> Bye,
> CzP
> 
> -------- Original Message --------
> Subject: 	Re: [packman] transcode
> Date: 	Sat, 01 Apr 2006 13:43:49 +0200
> From: 	Peter Czanik <pczanik at fang.fa.gau.hu>
> To: 	Henne Vogelsang <hvogel at hennevogel.de>
> References: 	<442C00A0.9060202 at fang.fa.gau.hu>
> <20060401100847.GC26967 at hennevogel.de>
> 
> 
> 
> Hello,
> 
> Henne Vogelsang wrote:
>> Hi,
>>
>> On Thursday, March 30, 2006 at 18:00:32, Peter Czanik wrote:
>>
>>   
>>> When I try to compile transcode with y2pmbuild, I get at the end of
>>> configure:
>>>
>>> ERROR: option '--enable-mjpegtools' failed: cannot compile
>>> mjpegtools/yuv4mpeg.h
>>> mjpegtools/yuv4mpeg.h can be found in the following packages:
>>>   mjpegtools  http://mjpeg.sourceforge.net/
>>>
>>> ERROR: option '--enable-imagemagick' failed: cannot link against libMagick
>>> libMagick can be found in the following packages:
>>>   ImageMagick  http://www.imagemagick.org/
>>>
>>> There is no such problem with using plain, old rpmbuild alone. Of
>>> course, I have mjpegtools and ImageMagick in the spec file together with
>>> the related -devel files. Any idea? Bye,
>>>     
>> Look into the config.log whats going wrong?
>>   
> Looked again, and found something strange. -L/usr/X11R6/lib seems to be
> missing from a configure check for some reason. It does not cause
> trouble outside y2pmbuild. The interesting part is:
> 
> configure:41715: checking for InitializeMagick in -lMagick
> configure:41745: gcc -o conftest -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -fmessage-length=0
> -D_FORTIFY_SOURCE=2 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 
> -L/usr/lib -L/opt/gnome/lib -lglib  conftest.c -lMagick -lz -lm -llcms
> -ltiff -lfreetype -ljpeg -lXext -lSM -lICE -lX11 -lXt -lbz2 -lpthread
> -lpthread -lm -lz -ldl  >&5
> /usr/bin/ld: cannot find -lXext
> collect2: ld returned 1 exit status
> configure:41751: $? = 1
> configure: failed program was:
> 
> And for mjpegtools:
> configure:39346: checking mjpegtools/yuv4mpeg.h usability
> configure:39358: gcc -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -O2 -g -fmessage-length=0
> -D_FORTIFY_SOURCE=2 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2
> -I/usr/include conftest.c >&5
> In file included from conftest.c:132:
> /usr/include/mjpegtools/yuv4mpeg.h:29:25: error: mjpeg_types.h: No such
> file or directory
> /usr/include/mjpegtools/yuv4mpeg.h:33:27: error: mjpeg_logging.h: No
> such file or directory
> In file included from conftest.c:132:
> /usr/include/mjpegtools/yuv4mpeg.h:465: error: expected ')' before 'level'
> configure:39364: $? = 1
> configure: failed program was:
> 
> The files are there, just -I/usr/include/mjpegtools is missing. Why does
> it work, when not using y2pmbuild? Bye,
> CzP
> 
> 
> 
> 
> _______________________________________________
> Packman mailing list
> Packman at links2linux.de
> http://www.links2linux.de/cgi-bin/mailman/listinfo/packman
> 
>