Find the answer to your Linux question:
Results 1 to 6 of 6
I'm trying to compile transcode-1.0.3, but I'm having trouble telling it where libavcodec is. This is the command I am using: Code: ./configure --prefix=$HOME CPPFLAGS="-I$HOME/include -I$HOME/include/ffmpeg -I$HOME/include/mpeg2dec" LDFLAGS="-L$HOME/lib" --with-libavcodec-includes=$HOME/include --with-libavcodec-libs=$HOME/lib ...
  1. #1
    Just Joined!
    Join Date
    Jul 2006
    Posts
    17

    Trouble Compiling transcode-1.0.3

    I'm trying to compile transcode-1.0.3, but I'm having trouble telling it where libavcodec is. This is the command I am using:

    Code:
    ./configure --prefix=$HOME CPPFLAGS="-I$HOME/include -I$HOME/include/ffmpeg -I$HOME/include/mpeg2dec" LDFLAGS="-L$HOME/lib" --with-libavcodec-includes=$HOME/include --with-libavcodec-libs=$HOME/lib
    The files $HOME/include/ffmpeg/avcodec.h and $HOME/lib/libavcodec.so exist, with the latter being a link to libavcodec.so.51.40.4.

    It gives me the following error:
    Code:
    ERROR: requirement failed: cannot link against libavcodec
    libavcodec can be found in the following packages:
      FFMpeg  http://www.ffmpeg.org/
    Any suggestions? Thanks.

  2. #2
    Linux Guru
    Join Date
    Nov 2004
    Posts
    6,110
    What distro are you using? There's a good chance that transcode is already available in your repositories.

    If you are intent on compiling from source I would think you need to install libavcodec first.

  3. #3
    Linux Guru fingal's Avatar
    Join Date
    Jul 2003
    Location
    Birmingham - UK
    Posts
    1,539
    Hi - interesting error. Which distro are you using? I only ask because I just did a Google search on:

    "ERROR: requirement failed: cannot link against libavcodec"

    and got several hits, but no solutions. Normally a problem like that is a common one, and I would have expected to find an answer quite easily.

    Sorry bigtom... I saw you get in there a little before my response. I see that libavcodec is just a component of the FFMpeg package.
    I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso

  4. #4
    Just Joined!
    Join Date
    Jul 2006
    Posts
    17
    It's on CentOS, but I don't have root access, so I can't install to /usr or use yum. I have to compile everything and put it in $HOME.

    Installing FFMpeg installed libavcodec as well. They come together.

    EDIT: Yeah, thanks for answering so quickly. I hope we can figure this out.

  5. #5
    Linux Guru fingal's Avatar
    Join Date
    Jul 2003
    Location
    Birmingham - UK
    Posts
    1,539
    It might sound overly simple, but take a step back and type ./configure --help . Look at the compile options, and enter them into a text editor. Read each step and check for any typos.

    Sometimes doing this can reveal that 'one tiny error' which is stopping things from working out.

    That's just a generic tip, but it might help. You can always cut and paste commands between the CLI and a text editor. Sometimes all that's wrong is a single character.

    Failing that, get a search together using key words from your efforts to get transcode working. For example:
    Code:
    transcode compile OR compiling problem OR problems OR error OR errors libavcodec
    A search like that can pull in some useful tips, but you might want to vary your strategy a bit. PS, this thread might be useful.
    I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso

  6. #6
    Just Joined!
    Join Date
    Jun 2009
    Posts
    1
    Hi there,

    I managed to fix this problem, eventually.

    First I downloaded the latest version of transcode (1.10)

    At first it wouldn't compile and I got error:

    Code:
    decode_mpeg2.c:142: undefined reference to `mpeg2convert_rgb24'
    I found that by editing import/Makefile to add:

    Code:
    LIBMPEG2_LIBS = -L/usr/lib -lmpeg2 -lmpeg2convert
    It worked OK.

    Hope this helps someone else.

    Thanks,

    Lou

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...