Question about missing dependencies in Slackware 14.2 multilib
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Question about missing dependencies in Slackware 14.2 multilib
Hi there everyone,
I first noticed this problem whilst trying to get the acestream software to install on my system the other day. So far I've only got it working under wine, which is fine, but there are packages for Ubuntu and Debian available as well as the source code.
However, when I tried to either compile the source or use the makepkg and deb2tgz tools I began to get errors saying that 6 libraries were 'not symbolic links'. Following this, other unrelated packages I did successfully install started issuing these warnings every time as well.
I've removed all of what remained of my clumsy efforts to get this to work and run ldconfig as root, so I don't get the messages about these libraries at the moment. But, if I run one of the scripts here: https://www.slackwiki.com/Dependency_Discovery
I still get this list of missing libraries. The avcodec and avformat ones, were two of the problems before.
What I'm asking is do I need to get these relevant 6 libraries sorted before I have a chance of getting the acestream software to work in my Linux and how do I do that? I noticed that with the code, it seemed to asking for older versions of libavcodec etc. - perhaps because its a couple of years old.
What I'm asking is do I need to get these relevant 6 libraries sorted before I have a chance of getting the acestream software to work in my Linux and how do I do that?
If those 6 libraries are dependent upon acestream working than yes; you will have to install them in the order in which they are listed.
With Slackware you have to satisfy the dependencies first. Once all of the dependencies are installed than you would proceed with the installation of the software.
Do do that you will have to go to the SlackBuilds repo, download them, run the SlackBuild script's, wait for the script to finish and than install them one at a time in the correct order <or> you can use sbopkg.
I'm not sure what script you ran to get that output (there were several on the page and I was too lazy to dig through the code to see what output matched which script), but have you verified those files don't exist and whether or not those packages were installed?
As for acestream, if you are using a pre-compiled binary, it might rely on older version of certain libraries. Trying to force installing older versions to support these dependencies could break other program already on the computer. Since you said it was available as source, have you considered compiling it? That should ensure it is built against the libraries already installed on your system rather than play the "dependency hell" game trying to match dependencies on your system with the ones required by the program.
That should ensure it is built against the libraries already installed on your system rather than play the "dependency hell" game trying to match dependencies on your system with the ones required by the program.
Most of the time I play the dependency hell game but that's because I was taught that way by a ancient master (frankbell) that was running Slack before there was a SlackBuilds repo:-
Is there a guarantee bassmadrigal, that by compiling from src that the lib's will be right?
Is there a guarantee bassmadrigal, that by compiling from src that the lib's will be right?
It can only build against what's installed in the system, so in that way, yes. However, it also depends on the requirements of the program. If it requires older or newer versions of libraries, then it may not be able to be compiled.
However, now that I'm at a point where I can look into this more (the acestream site is blocked at my work), it looks like this would be quite the project to build as it requires you to build vlc during the process (which means all the dependencies of vlc). I wasn't willing to dig into it too much more than that.
Thanks for answering my question.
I very rarely compile from src and needing other older and or a mix of newer lib's is one of the reasons I don't compile.
Also, another one of our members here advised me a long time ago not to mix compiling from src and programs from the SlackBuilds repo. If I recall correctly it's not good for the system.
======***=======*******======******======******======******======******======
Yup looking at that page that OP posted all the depends for vlc are required so if it were my system I probably wouldn't pursue it:-
Code:
Compile for Linux:
Tested only on Ubuntu
Install build tools libtool, build-essential, pkg-config, autoconf
Checkout all required libraries to build vlc
Also install libqt4-webkit, openssl, sqlite3
Edit config.sh, set HOST="", to build for your system.
./bootstrap.sh
./configure.sh
cd build-ace
make
make install
Since I already build vlc and deps from source anyway, I was somewhat intrigued by this project. However looking at the instructions, I noticed that vlc version 2.1.5 was mentioned - very old. Then I saw that the latest change to the source code repo itself was in 2014. That's where I stopped looking - or maybe I was looking in the wrong place (https://bitbucket.org/AceStream/acestreamplayer/src)?
Also, another one of our members here advised me a long time ago not to mix compiling from src and programs from the SlackBuilds repo.
But programs from SlackBuilds ARE compiled from source, but through a script (SlackBuild), supplied BY that website. They have just already decided which options to configure the package with.
If those 6 libraries are dependent upon acestream working than yes; you will have to install them in the order in which they are listed.
With Slackware you have to satisfy the dependencies first. Once all of the dependencies are installed than you would proceed with the installation of the software.
Do do that you will have to go to the SlackBuilds repo, download them, run the SlackBuild script's, wait for the script to finish and than install them one at a time in the correct order <or> you can use sbopkg.
You mentioned Ubuntu and Debian in the beginning of your post.
Have you been able to install acestream on those distro's w/o wine?
OK, I've tried installing the dependencies for VLC (as suggested by the build instructions with the code) using sbopkg, but lots of them come back with errors.
I don't know how I've managed to get so many 'gaps' in my system already, but lots of things won't build with sbopkg because it cannot find things.
But, if I run the SlackBuild scripts individually, often they will work that way instead.
No, I'm not running ubuntu or debian, so I haven't tried those packages on those distros.
Thanks for answering my question.
I very rarely compile from src and needing other older and or a mix of newer lib's is one of the reasons I don't compile.
This is really not very common. Most programs compiled from source have a wide range of versions they're able to support. Only occasionally have I run into issues where the program wants a newer version of library than what I have installed. And you tend to only run into issues with programs wanting older versions of a library if the library had a substantial rewrite or the program hasn't been updated in a long time (back when the kernel went from 2.6 to 3.0, a lot of programs relying on the kernel wouldn't compile because they only checked for a 2.6.x version and didn't look for anything 2.6 or greater.
The problem is much more likely to happen when you use pre-compiled binaries. If you get binaries that are designed for 14.2 (or -current, if you're running that), you won't typically run into problems since the dependencies should match what's already installed on the system. But if you try and take a package from -current and install it on 14.2, many times it won't work because it depends on a specific version of a library that's in -current and not in 14.2. This also applies when you take pre-compiled binaries for other distros. The likelihood of having the same dependency versions goes down drastically.
Luckily, many libraries, while they may have different versions, sport the same ABI, so multiple versions will have the same compatibility and will work without issue. This is why, while still not very likely, it is much more likely to run into issues with pre-compiled binaries rather than building from source. If you look at -current's changelog and search for "Shared library .so-version bump.", you can see that while this happens occasionally, it's not a normal thing. But sometimes when that library needs to be updated, it causes a massive amount of packages to be rebuilt, because they all rely on the older version (an upgraded openssl required 61 packages to be rebuilt).
Quote:
Originally Posted by Ztcoracat
Also, another one of our members here advised me a long time ago not to mix compiling from src and programs from the SlackBuilds repo. If I recall correctly it's not good for the system.
As ehartman stated, most of the SlackBuild from SBo are compiling the software from source. What that member likely meant was that self-compiling software typically installs into /usr/local/, where SlackBuilds tend to install into /usr/. While this isn't typically an issue by itself, items installed into /usr/local/ aren't typically tracked by the package manager and most of the time, things in /usr/local/ have precedence over /usr/, which means if you manually compile fakeprog-2.0 and it is installed into /usr/local/, but you find it doesn't work and then find a fakeprog-1.0 SlackBuild that is supposed to work and it is installed into /usr/, most programs are going to look at the fakeprog-2.0 installed into /usr/local/, and unless you kept the source, you can't uninstall it easily.
This is an unlikely example, but I typically don't recommend manually compiling and installing software since it won't be tracked by the package manager and makes it more difficult to uninstall. If I need to build something that doesn't have a SlackBuild, I'll figure out the compile options by manually compiling it, but NOT installing it. Then I'll create a SlackBuild so that I can create a package that can be installed.
The thing I see more frequently on the forum is don't mix and match binary packages from multiple repos, as they might have different versions of dependencies they rely on. You tend to not run into problems if they're standalone repos, only designed to install one thing (ktown, mate, etc). And, while I don't know if this is intentional, it seems like Eric's repo tends to mix with repos based off of SBo pretty well.
Sorry for the novel...
Last edited by bassmadrigal; 12-04-2018 at 10:51 AM.
I'm not sure what script you ran to get that output (there were several on the page and I was too lazy to dig through the code to see what output matched which script), but have you verified those files don't exist and whether or not those packages were installed?
As for acestream, if you are using a pre-compiled binary, it might rely on older version of certain libraries. Trying to force installing older versions to support these dependencies could break other program already on the computer. Since you said it was available as source, have you considered compiling it? That should ensure it is built against the libraries already installed on your system rather than play the "dependency hell" game trying to match dependencies on your system with the ones required by the program.
Those files DO exist, in the case of for example, libavcodec.
EDIT: Actually, they don't, do they - comparing the two lists! But the problem when I tried to compile the code, was that the required libraries weren't symbolic links. Which I looked up and it was suggested to delete one version of the file and then create a symlink to another, with the required name.
However, that list above is different to what I had on Sunday - there were 3 versions of libavcodec in the /lib folder, each with a more precise name (libavcodec.so.56 ... libavcodec.so.56.123, or whatever). The error messages were telling me that the problem was that none of them were symbolic links. And they weren't, they were regular files, I think.
Last edited by Pipeline79; 12-04-2018 at 11:04 AM.
However, that list above is different to what I had on Sunday - there were 3 versions of libavcodec in the /lib folder, each with a more precise name (libavcodec.so.56 ... libavcodec.so.56.123, or whatever). The error messages were telling me that the problem was that none of them were symbolic links. And they weren't, they were regular files, I think.
If this is a stock Slackware 14.2 install, the files should be symlinks. On my system, I have the following:
Can you provide us the actual error message? And what you're doing to get it? Once I get home, I may be able to try things out to get a working version and let you know what you need to do.
If you don't mind me asking, why not just use VLC or Amarok?
No, I don't mind you asking. I don't know if you've used the acestream software or not, but it has a couple of components, the ace-player is just like vlc, but the 'ace-engine' is the server which you need to have running to connect to the swarm of people sharing the stream. I don't think you can access these streams which have 'Content IDs' without having the engine/server running and I don't think you can access them using regular VLC alone. The windows package installs all of this at once. I do have VLC 3 installed from alienbob, because I can access the acestream server on a localhost webpage, and send the stream through VLC to my chromecast - whereas doing it direct from a browser or from the ace-player to chromecast doesn't seem to work.
All that slackware needs is to have the ace-engine part running, therefore. I guess the source code is building this ace-player as well, which is unnecessary.
I might be wrong, however - perhaps there is a way to connect to these streams from ordinary media players that I haven't tried.
Can you provide us the actual error message? And what you're doing to get it? Once I get home, I may be able to try things out to get a working version and let you know what you need to do.
Right, I know now where the extra versions of libavcodec.so and so on came from now (that caused the error messages). They came from the debian package on that webpage which I tried extracting, making into a package and installing. Now that I've removed that, they're gone.
As for the code, it has a config.sh, a bootstrap.sh and configure.sh. The config.sh you're supposed to edit for your 'HOST', then run bootstrap.sh. Somehow I got through the bootstrap part before, just by changing the HOST type to "x86_64" from "i686-w64-mingw32". You can also edit the VLC version, which is 2.1.5, as someone said. I tried changing that to 3.0.4 just now. Neither version will work now, anyway. I get:
Code:
vlc-3.0.4/config.h.in
vlc-3.0.4/make-alias
vlc-3.0.4/ChangeLog
\033[33mInfo:\033[0m Applying patch: /home/kevin/build/acestreamplayer/patches/10-locale.patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ru vlc-2.1.2.orig/po/acestreamplayer.pot vlc-2.1.2/po/acestreamplayer.pot
|--- vlc-2.1.2.orig/po/acestreamplayer.pot 2014-07-06 19:54:01.000000000 +0300
|+++ vlc-2.1.2/po/acestreamplayer.pot 2014-10-28 13:11:31.320150970 +0200
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
patching file po/en_GB.po
Hunk #1 FAILED at 10086.
Hunk #2 FAILED at 31524.
Hunk #3 FAILED at 35411.
3 out of 3 hunks FAILED -- saving rejects to file po/en_GB.po.rej
patching file po/Makevars
Hunk #1 succeeded at 3 with fuzz 1.
patching file po/POTFILES.in
Hunk #1 FAILED at 1176.
1 out of 1 hunk FAILED -- saving rejects to file po/POTFILES.in.rej
patching file po/ru.po
Hunk #1 succeeded at 10037 with fuzz 2 (offset 331 lines).
Hunk #2 succeeded at 36580 (offset 3130 lines).
Hunk #3 FAILED at 34746.
1 out of 3 hunks FAILED -- saving rejects to file po/ru.po.rej
patching file po/uk.po
Hunk #1 succeeded at 10043 with fuzz 2 (offset 318 lines).
Hunk #2 FAILED at 34007.
Hunk #3 FAILED at 36308.
2 out of 3 hunks FAILED -- saving rejects to file po/uk.po.rej
\033[31mError:\033[0m Cannot apply patch /home/kevin/build/acestreamplayer/patches/10-locale.patch
And, if I try using sbopkg to build the dependencies for the latest vlc on there first, as I should - loads of them won't.
The first one that fails is libbluray. I.e.:
Code:
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for library containing pthread_create... -lpthread
checking for library containing dlopen... -ldl
checking for pkg-config... /home/kevin/.linuxbrew/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBXML2... no
configure: error: Package requirements (libxml-2.0 >= 2.6) were not met:
No package 'libxml-2.0' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBXML2_CFLAGS
and LIBXML2_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
libbluray:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?:
But I do actually have it installed:
Code:
Looking for libxml in package list. Please wait... DONE
The list below shows all packages with name matching "libxml".
[ Status ] [ Repository ] [ Package ]
installed multilib libxml2-compat32-2.9.5-x86_64-1_slack14.2compat32
installed patches libxml2-2.9.5-x86_64-1_slack14.2
uninstalled(masked) slackware64 libxml2-2.9.4-x86_64-2
You can search specific files using "slackpkg file-search file".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
ackage_management
