MY PC: Slackware64-Current | Minimal custom installation

Trying to run the Software Clementine!

Problem: When install ffmpeg-3.1.1-x86_64-1alien.txz or ffmpeg-3.0.2-x86_64-1gv.txz

I create the necessary shortcuts:
libavcodec.so.56 > libavcodec.so.57.48.101
libavutil.so.54 > libavutil.so.55.28.100

Appear the errors below:
clementine: /usr/lib64/libavcodec.so.56: version `LIBAVCODEC_56' not found (required by /usr/lib64/libchromaprint.so.0)
clementine: /usr/lib64/libavutil.so.54: version `LIBAVUTIL_54' not found (required by /usr/lib64/libchromaprint.so.0)

OBS: Only works with ffmpeg-2.8-x86_64-1alien.txz
OBS 2: chromaprint-1.2-x86_64-5_slack.txz installed

What is going on? How can I use the latest versions?

Easy answer is to build it for yourself. You'd probably have to change your installation to full to preclude build errors. Don't forget to build the dependencies.

https://slackbuilds.org/repository/1...io/clementine/

I don't understand what you mean?
What would be missing dependence between these 2 Packages (ffmpeg-3.1.1-x86_64-1alien.txz X ffmpeg-2.8-x86_64-1alien.txz) being that they have the same files, only with different versions?

I would like to remind you that the Clementine WORKS with the Package ffmpeg-2.8-x86_64-1alien.txz

I meant that you won't be able to build the clementine package without having built the other packages that clementine needs first. Those other packages may require yet other packages to be built themselves.

Creating those symlinks is not going to work with programs depending on ffmpeg...

...as this comment shows.

At a minimum you need to recompile chromaprint because its libraries complain about the wrong ffmpeg version. Perhaps you need to recompile Clementine as well but hopefully not.

1 members found this post helpful.

Okay. But it would not be the case. I did not build anything. I'm using a Package ready (clementine-1.3.1-x86_64-1_slonly.txz) and another test installed directly Source (Clementine-1.3.1.tar.gz)

There are several already built here:
http://slakfinder.org/index.php?act=...&file=#results

I can not understand is why I can not update ffmpeg. What does this have to do with the installation of clementine? I think it is not indifferent?

I think it's really the problem because it points the libchromaprint. I will study it!

My point is the amount of time that you have wasted trying to force incompatible libraries to act as if they were compatible is probably greater than the amount of time it would have taken to use slackbuilds to build everything that you need to install a working version of Clementine.

1 members found this post helpful.

You need to stop using so much bold-face text and start learning about library versions and ABI incompatibilities.
This is nothing new. Why do you think in Slackware it is sometimes needed to recompile multiple packages when a single core library is updated? That is because of the way dynamic library linking works. Clementine uses libchromaprint, and libchromaprint uses libavcodec. If you change a lower-level library, the consequences of that will work their way up to the calling program - Clementine.

And only a recompilation will help to let libchromaprint know about the new library version of libavcodec and friends.

This issue (updating ffmpeg shared libraries breaks a lot of programs that link to them) is one of the high-ranking topics in discussion forums of Ubuntu-like distros. Ubuntu users show the same level of incomprehension you do in this thread... but they usually do not know how to recompile a package, whereas you should know how to fix the issue by recompiling one or more packages.

This is also the reason why Slackware puts statically compiled ffmpeg libraries inside some of its packages (xine, mplayer) to prevent this kind of breakage.

3 members found this post helpful.

It's not a file name problem, it's an ABI problem, and the fact that the version numbers are different makes all the difference. The first number after the library name is typically used to indicate the "major" revision number of that library's ABI. Different major revision numbers are usually ABI-incompatible: that's why you can (usually) symlink libwhatever.so.1.8 to libwhatever.so.1.10 so a program that was compiled against libwhatever 1.8 will work on your libwhatever 1.10 system without recompilation, but (usually) can't do the same to make a program work if it was compiled against libwhatever 0.2.

You'd be doing yourself a massive favour by removing those libav* symlinks now, before you forget and break a ton of other stuff further down the line.

That's because the Chromaprint package you've installed was compiled against ffmpeg 2.8. The libraries provided by ffmpeg 3.0 and above have different ABIs to the libraries in ffmpeg 2.8, so newer versions won't work unless you recompile Chromaprint against the newer version of ffmpeg. You might be able to get away with simply recompiling the version of Chromaprint that's already installed, but the ffmpeg API was also changed substantially for 3.0, and you'll have to upgrade to a version of Chromaprint that's compatible with the ffmpeg 3.0 API if the version you're using now doesn't know how to use it. If you have to do this, Clementine will also break if Chromaprint's ABI has changed between the version you had installed and the version you upgrade to; in that case, you'll also need to recompile or upgrade Clementine.

tl;dr: either use a set of precompiled packages from the same source (hint: look at the tag, after the last hyphen and before the ".txz" in the file name), or compile everything yourself from the SlackBuilds. Until you know what you're doing, mixing and matching is a recipe for disaster. (If it makes you feel any better, repeatedly breaking and fixing things is the process by which you come to know what you're doing. )