On Thu, Mar 22, 2012 at 1:30 AM, John David Anglin dave.ang...@bell.net wrote:
On 20-Mar-12, at 9:54 PM, Andres Mejia wrote:
This issue is common if you're using the libav-extra libraries. It's
likely a broken symlink from your *.so files.
I don't think so. Updating libgcrypt11 to 1.5.0-3
On 29-Apr-12, at 4:40 AM, Reinhard Tartler wrote:
On Thu, Mar 22, 2012 at 1:30 AM, John David Anglin dave.ang...@bell.net
wrote:
On 20-Mar-12, at 9:54 PM, Andres Mejia wrote:
This issue is common if you're using the libav-extra libraries. It's
likely a broken symlink from your *.so files.
On 20-Mar-12, at 9:54 PM, Andres Mejia wrote:
This issue is common if you're using the libav-extra libraries. It's
likely a broken symlink from your *.so files.
I don't think so. Updating libgcrypt11 to 1.5.0-3 fixes the build.
Somehow,
it eliminates the dependency.
Dave
--
John David
Source: libav
Version: 4:0.8.1-1
Severity: normal
gcc -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavutil
-Llibpostproc -Llibswscale -Wl,--as-needed -Wl,--warn-common
-Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil
-o ffmpeg ff
On Tue, Mar 20, 2012 at 9:24 PM, Dave Anglin dave.ang...@bell.net wrote:
Source: libav
Version: 4:0.8.1-1
Severity: normal
gcc -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavutil
-Llibpostproc -Llibswscale -Wl,--as-needed -Wl,--warn-common
5 matches
Mail list logo