[Fwd: Re: [packman] transcode]

Sat Apr 1 19:12:19 CEST 2006

Hi Peter,

this is strange. Are you sure, you are compiling version 1.0.2? Are you
using my spec file? Here is there relevant part from my build:

> 			 || test ! -s conftest.err
> configure:40130: $? = 0
> configure:40133: test -s conftest
> configure:40136: $? = 0
> configure:40149: result: yes
> configure:40218: checking whether mjpegtools support is requested
> configure:40233: result: yes
> configure:40273: checking for pkgconfig support for mjpegtools
> configure:40280: result: yes
> configure:40292: checking for mjpegtools-config
> configure:40310: found /usr/bin/mjpegtools-config
> configure:40323: result: /usr/bin/mjpegtools-config
> configure:40336: checking how to determine MJPEGTOOLS_CFLAGS
> configure:40345: result: pkg-config
> configure:40390: checking mjpegtools/yuv4mpeg.h usability
> configure:40402: gcc -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -I/usr/include/mjpegtools -I/usr/include/mjpegtools/mpeg2enc -I/usr/include/mjpegtools/mplex conftest.c >&5
> configure:40408: $? = 0
> configure:40412: test -z 
> 			 || test ! -s conftest.err
> configure:40415: $? = 0
> configure:40418: test -s conftest.o
> configure:40421: $? = 0
> configure:40431: result: yes
> configure:40435: checking mjpegtools/yuv4mpeg.h presence
> configure:40445: gcc -E -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -I/usr/include/mjpegtools -I/usr/include/mjpegtools/mpeg2enc -I/usr/include/mjpegtools/mplex conftest.c
> configure:40451: $? = 0
> configure:40471: result: yes
> configure:40506: checking for mjpegtools/yuv4mpeg.h
> configure:40513: result: yes
> configure:40546: checking how to determine MJPEGTOOLS_LIBS
> configure:40555: result: pkg-config
> configure:40595: checking for y4m_si_get_height in -lmjpegutils
> configure:40625: gcc -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2  -L/usr/lib -L/opt/gnome/lib -lglib  conftest.c -lmjpegutils  -lm -lz -ldl  >&5
> configure:40631: $? = 0
> configure:40635: test -z 
> 			 || test ! -s conftest.err
> configure:40638: $? = 0
> configure:40641: test -s conftest
> configure:40644: $? = 0
> configure:40657: result: yes
> configure:40724: gcc -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -I/usr/include/mjpegtools -I/usr/include/mjpegtools/mpeg2enc -I/usr/include/mjpegtools/mplex -O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2  -L/usr/lib -L/opt/gnome/lib -lglib conftest.c -lm -lz -ldl   -lmjpegutils  >&5
> configure:40730: $? = 0
> configure:40734: test -z 
> 			 || test ! -s conftest.err
> configure:40737: $? = 0
> configure:40740: test -s conftest
> configure:40743: $? = 0

rgds, Rainer

Peter Czanik schrieb:
> Hello,
> Yes, it's there in the chroot-ed environment created by y2pmbuild. The
> problem is, that for some reason, the related part of configure does not
> have -I/usr/include/mjpegtools, and this way it can not find the
> includes from that directory. Why is it no problem outside of y2pmbuild,
> or better: why is it problem for y2pmbuild? Bye,
> CzP
> 
> Rainer Lay wrote:
>> 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
>>>
>>>
>>>     
> 
> 