Re: Building against ffmpeg libraries from jessie-backports causes version conflict warnings
Hi Joseph,
2016-10-09 12:37 GMT+02:00 Joseph Heenan <joseph@heenan.me.uk>:
> Hi,
>
> Using the ffmpeg libraries from jessie-backports results in some
> linker warnings. Another user already ran into this, but I think
> posted to the wrong list[1], so I'll simply repeat his explanation
> below, which seems correct to me.
>
> Thanks
>
> Joseph
>
>
>
> I'm trying to build against libavformat-dev, libavcodec-dev, and
> libavutil-dev from jessie-backports. When I build, I get these
> warnings:
>
> /usr/bin/ld: warning: libavcodec.so.56, needed
> by //usr/lib/x86_64-linux-gnu/libchromaprint.so.0, may conflict with
> libavcodec.so.57
>
> /usr/bin/ld: warning: libavutil.so.54, needed
> by //usr/lib/x86_64-linux-gnu/libchromaprint.so.0, may conflict with
> libavutil.so.55
OK, those can be observed here, too:
https://buildd.debian.org/status/fetch.php?pkg=kodi&arch=i386&ver=16.1%2Bdfsg1-2~bpo8%2B1&stamp=1474951910
>
> It looks like this is the issue:
> - In jessie-backports, libavcodec-dev depends on libavcodec57, and
> libavutil-dev depends on libavutil55
> - In jessie-backports, libavformat-dev depends on libavformat57, which
> depends on libchromaprint0 from jessie, which depends on libavcodec56
> and libavutil54. Thus, libavcodec56 and libavutil54 conflict with
> libavcodec57 and libavutil55.
>
> It seems like the most obvious fix would be backporting libchromaprint0
> from stretch, as it correctly depends on libavcodec57 and libavutil55 in
> stretch.
There is a circular build-dependency between ffmpeg and chromaprint.
I'm updating chromaprint now and ffmpeg with the next upload.
Maybe it would be a good idea to check all packages in jessie-backports
for circular dependencies.
Cheers,
Balint
>
>
> [1] https://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2016-June/051908.html
>
Reply to: