StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POVim can't find C++ libavformat/libavutil library (No such file or directory)
text
Body
copied!<p>Loading up the <a href="https://github.com/pukster/omxplayer/blob/master/OMXReader.cpp" rel="nofollow">omxplayer.cpp</a> file in vim and it gives me the following error:</p> <blockquote> <p>omxplayer.cpp|34 col 34| fatal error: libavformat/avformat.h: No such file or directory</p> </blockquote> <p>This is where the problem is occurring</p> <pre><code>#include <libavformat/avformat.h> #include <libavutil/avutil.h> </code></pre> <p>But I know the files exist:</p> <pre><code>$ ls -l /usr/lib/libavu* lrwxrwxrwx 1 root root 28 2013-11-08 13:46 /usr/lib/libavutil.so -> /usr/lib/libavutil.so.51.7.0 lrwxrwxrwx 1 root root 19 2012-06-13 12:38 /usr/lib/libavutil.so.51 -> libavutil.so.51.7.0 -rw-r--r-- 1 root root 117212 2012-06-13 12:38 /usr/lib/libavutil.so.51.7.0 $ ls -l /usr/lib/libavf* lrwxrwxrwx 1 root root 30 2013-11-08 13:29 /usr/lib/libavformat.so -> /usr/lib/libavformat.so.53.3.0 lrwxrwxrwx 1 root root 21 2012-06-13 12:38 /usr/lib/libavformat.so.53 -> libavformat.so.53.3.0 -rw-r--r-- 1 root root 1053000 2012-06-13 12:38 /usr/lib/libavformat.so.53.3.0 </code></pre> <p>And <code>ldconfig</code> can also find them:</p> <pre><code>$ ldconfig -p | grep libavformat && ldconfig -p | grep libavutil libavformat.so.53 (libc6, hwcap: 0x0008000000008000) => /usr/lib/i686/cmov/libavformat.so.53 libavformat.so.53 (libc6) => /usr/lib/libavformat.so.53 libavutil.so.51 (libc6, hwcap: 0x0008000000008000) => /usr/lib/i686/cmov/libavutil.so.51 libavutil.so.51 (libc6) => /usr/lib/libavutil.so.51 </code></pre> <p>I have read somewhere that ldconfig is for run time whereas ld is for build time, however, in this case I know the libraries are there in /usr/lib, therefore, what could be causing this problem?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload