Re: [transcode-users] transcode 1.0 configure problem

[Jacob Meuser <jakemsr@xxxxxxxxxxx>]

On Sun, Jul 31, 2005 at 08:22:43PM +0100, Robert Flint wrote:
> I have been succesfully using transcode 0.6.14 on my SUSE 9.0 box for some 
> time and decided to compile 1.0.0 today.
> 
> I keep getting the same problem though when running ./configure. It complains 
> that:
> 
> ERROR: requirement failed: cannot link against libmpeg2
> libmpeg2 can be found in the following packages:
>   mpeg2dec  http://libmpeg2.sourceforge.net/
> 
> 
> Please see the INSTALL file in the top directory of the
> transcode sources for more information about building
> transcode with this configure script.
> 
> 
> I downloaded and successfully compiled libmpeg2 but farther up the 
> ./configure 
> output I see the following:
> 
> checking mpeg2dec/mpeg2.h usability... no
> checking mpeg2dec/mpeg2.h presence... yes
> configure: WARNING: mpeg2dec/mpeg2.h: present but cannot be compiled
> configure: WARNING: mpeg2dec/mpeg2.h:     check for missing prerequisite 
> headers?
> configure: WARNING: mpeg2dec/mpeg2.h: see the Autoconf documentation
> configure: WARNING: mpeg2dec/mpeg2.h:     section "Present But Cannot Be 
> Compiled"
> configure: WARNING: mpeg2dec/mpeg2.h: proceeding with the preprocessor's 
> result
> configure: WARNING: mpeg2dec/mpeg2.h: in the future, the compiler will take 
> precedence
> configure: WARNING:     ## ------------------------------------ ##
> configure: WARNING:     ## Report this to the transcode lists.  ##
> configure: WARNING:     ## ------------------------------------ ##
> checking for mpeg2dec/mpeg2.h... yes
> checking how to determine LIBMPEG2_LIBS... prefix
> checking for mpeg2_init in -lmpeg2... no
> 
> 
> Everything appears to be present but for some reason it cannot be used. I am 
> using the following options in ./configure:
> 
> 
> 
> ./configure --enable-mjpegtools --enable-avifile --enable-ogg --enable-vorbis 
> --enable-libdv --enable-gtk
> 
> 
> 
> Any advice would be much appreciated.

look for the output of this test in config.log.  that should give
you the reason the linking test failed.

-- 
<jakemsr@xxxxxxxxxxx>