[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
pkg/47582: libavutil.so major version collision w/ffmpeg vs. ffmpeg010
>Synopsis: libavutil.so major version collision w/ffmpeg vs. ffmpeg010
>Arrival-Date: Fri Feb 22 07:15:00 +0000 2013
>Originator: John D. Baker
>Release: NetBSD 6.1_RC1/amd64, pkgsrc-2012Q4
NetBSD skuld 6.1_RC1 NetBSD 6.1_RC1 (SKULD) #16: Wed Feb 20 01:07:18 CST 2013
"multimedia/ffmpeg" and "multimedia/ffmpeg010" both include
"libavutil.so.51". This can (and has) confused applications that need
the older "ffmpeg010" package, but also have "ffmpeg" (v1.0.1) installed.
When such an application asks for "libavformat.so.53", the linker finds
it in "/usr/pkg/lib/ffmpeg010/libavformat.so.53". When subsequently
asked for "libavutil.so.51", the linker finds it in
"/usr/pkg/lib/libavutil.so.51". The application fails, likely with
much complaining about inability to find codecs and spewing messages
with bizarre numbers which appear to represent addresses or offsets.
On a system with pkgsrc-2012Q4 and an up-to-date "pkgsrc-wip",
install "wip/electricsheep-svn" (bringing in "multimedia/ffmpeg010" as
Then install "multimedia/ffmpeg" (or a package which depends on it).
Attempt to run 'electricsheep'.
Also "ktruss -i electricsheep" and watch the shared libraries being
Is there a way to force linking against the full library version?
"ffmpeg010" has "libavutil.so.51.35.100" while "ffmpeg" has version
Alternatively, pull up ffmpeg (v1.1.x) from HEAD as it has
"libavutil.so.52" which will eliminate the collision at the major version
There may yet be a problem as libpostproc.so.52, libswresample.so.0, and
libswscale.so.2 still collide between the two versions of ffmpeg.
Main Index |
Thread Index |