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.
Are you sure you have the right packages installed? libpthread is part of the l/glibc package. If you happened to install the 32bit Slackware, it would make sense why it can't find libpthread.so, because the 64bit package would be looking for the 64bit version of libpthread and you only have the 32bit version installed.
If you are running the 64bit version of Slackware, then you're either missing your glibc package (not likely, because I'd imagine other things would be broken) or you have a broken install.
Extreme Tux Racer should be able to be launched using the etr binary located under /usr/games/ (which should be in your PATH, so you should be able to just type etr in the CLI). Super Tux can be run just using supertux and Super Tux Kart can be run using supertuxkart.
I don't have ibus on my system, so I'm not sure what to run. You could check /var/log/packages/ibus-1.3.9-x86_64-2_slonly and see if it has anything in the /usr/bin/ directory.
Are you sure you have the right packages installed? libpthread is part of the l/glibc package. If you happened to install the 32bit Slackware, it would make sense why it can't find libpthread.so, because the 64bit package would be looking for the 64bit version of libpthread and you only have the 32bit version installed.
If you are running the 64bit version of Slackware, then you're either missing your glibc package (not likely, because I'd imagine other things would be broken) or you have a broken install.
Extreme Tux Racer should be able to be launched using the etr binary located under /usr/games/ (which should be in your PATH, so you should be able to just type etr in the CLI). Super Tux can be run just using supertux and Super Tux Kart can be run using supertuxkart.
I don't have ibus on my system, so I'm not sure what to run. You could check /var/log/packages/ibus-1.3.9-x86_64-2_slonly and see if it has anything in the /usr/bin/ directory.
Extreme Tux Racer
Code:
etr: error while loading shared libraries: libsfml-system.so.2.4: cannot open shared object file: No such file or directory
ibus-daemon
Code:
current session already has an ibus-daemon.
ibus-setup
Code:
Traceback (most recent call last):
File "/usr/share/ibus/setup/main.py", line 31, in <module>
import ibus
File "/usr/lib64/python2.7/site-packages/ibus/__init__.py", line 26, in <module>
from common import *
File "/usr/lib64/python2.7/site-packages/ibus/common.py", line 54, in <module>
from xdg import BaseDirectory
ImportError: No module named xdg
SuperTuxKart
Code:
supertuxkart: error while loading shared libraries: libopenal.so.1: cannot open shared object file: No such file or directory
Seems like there are some missing libraries. Should I install the library to make it work?
Last edited by limpingstone; 04-29-2017 at 10:15 PM.
Ok, well for Extreme Tux Racer and Super Tux Kart, you're missing some required dependencies. Mainly SFML and OpenAL. Super Tux has several other required dependencies, but it'd be easier to just link to that page. (NOTE: some of those dependencies have dependencies of their own, so make sure you check out each one). ibus is missing pyxdg.
This is one of the issues when you download precompiled packages. You need to make sure they don't have any dependencies, since the package won't usually include them.
But this still doesn't answer if you have 32bit or 64bit Slackware installed. What's the output of the following command?
It does look as if you have missing dependencies. Compile scripts will commonly throw errors if dependencies are missing. Did any of your compile scripts throw errors?
Slackbuilds.org commonly lists the dependencies that various packages require.
It is wise to drill down through the list(s) of dependencies (some dependencies may have dependencies of their own) to reach the last ones on the list and then to install them, working your way from the last on the list up to the desired package, until you reach the desired package.
Ok, well for Extreme Tux Racer and Super Tux Kart, you're missing some required dependencies. Mainly SFML and OpenAL. Super Tux has several other required dependencies, but it'd be easier to just link to that page. (NOTE: some of those dependencies have dependencies of their own, so make sure you check out each one). ibus is missing pyxdg.
This is one of the issues when you download precompiled packages. You need to make sure they don't have any dependencies, since the package won't usually include them.
But this still doesn't answer if you have 32bit or 64bit Slackware installed. What's the output of the following command?
Code:
ls /var/log/packages/etc-*
Thanks for the link.
I am running a 64-bit Slackware, and for the code, I got:
It does look as if you have missing dependencies. Compile scripts will commonly throw errors if dependencies are missing. Did any of your compile scripts throw errors?
Slackbuilds.org commonly lists the dependencies that various packages require.
It is wise to drill down through the list(s) of dependencies (some dependencies may have dependencies of their own) to reach the last ones on the list and then to install them, working your way from the last on the list up to the desired package, until you reach the desired package.
Before I installed the programs using a binary package, I compiled and installed them on another system, so I understand the importance of those libraries during the compiling process. However, I thought that the binary packages are already compiled and no longer need a binary. I wonder if it is caused by other problems, since the packages I compiled before wasn't working either.
Before I installed the programs using a binary package, I compiled and installed them on another system, so I understand the importance of those libraries during the compiling process. However, I thought that the binary packages are already compiled and no longer need a binary. I wonder if it is caused by other problems, since the packages I compiled before wasn't working either.
"shared library" means that the library is (or at least can be) shared between programs that need it at run time. So they can be included, in other words built in, or not, in the binaries of programs that need them.
There are two main reasons why to choose not to include, in other words statically link, a library in a binary:
because if this library is already shipped in your system this results in a waste of space on disk,
because if you need to upgrade this library, not to get new features but just as a security fix, you will have to rebuild all binaries that need it if they have it built in.
There are a few cases where the maintainer of a package chooses to statically link libraries. An example that comes to mind is the vlc provided by Eric Hameleers (Alien BoB): this helps the end user to use it without having to build and install the many packages that ship libraries that it needs, some providing optional features. But for Eric this means an extra work, thanks to him.
tl;dr: if an error message says that you miss a shared library, install the package that provides it.
Last edited by Didier Spaier; 04-29-2017 at 11:39 PM.
Ok, knowing now that you are for sure running 64bit Slackware, your wine error is likely due to not having multilib installed. Eric's wine package includes the ability to run both 32bit and 64bit Windows programs and requires multilib for it to function properly.
Quote:
The Wine package I provide for the 64bit Slackware therefore mimicks this WoW64 configuration and offers both a 32bit “wine” and a 64bit “wine64” environment. You still need multilib to make this work on Slackware64 but you will be able to run 64bit Windows binaries just as easily as 32bit Windows programs.
Also, don't forget to check dependencies for wine. If any of Eric's packages require dependencies, he'll have them listed in a .dep file under the directory the package is in. If the package requires multilib, you'll also need the 32bit versions and run convertpkg-compat32 on them (which is included in the multilib tools). In this case, it will require OpenAL and libva.
As far as your other packages, as others have stated, they still require the dependencies that were used to compile them. Slackware doesn't differentiate between compiling dependencies and runtime dependencies, so it is just best to ensure all dependencies used to build the package are available when you install the package somewhere else
And it's actually a good thing that everything isn't compiled with static libraries as it can increase the size substantially. For example. if you compile vlc from SBo, the package is around 10MB. If you use Eric's package, it is around 40MB. It's not a big deal with one or two packages (especially in the case of VLC since it has so many dependencies and changing just one can break the package), but if you need those dependencies used in VLC in another program, they'd have to be installed twice (if shared -- or if statically included, it'd have to be built into each program, taking up space each time). Shared libraries help cut down on the installation size and minimize compiling when you need to include those libraries in multiple places.
Thank you everyone! The Supertux, Etr, Supertuxkart and iBus are all working fine and I am having a lot of fun!
It is only wine that is left to solve. I checked glibc and libva, which are all the dependencies for Wine, and they are all installed already. The same error message still pops up when I type in winecfg into the CLI.
Code:
bash-4.3$ winecfg
/usr/bin/wine: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory
Is it because of the multilib?
How do I find and install multilib?
Yes, as I mentioned earlier, the wine package provided by Eric (alien bob) requires multilib. There's a SlackDocs page on it as well as Eric's direct site. Multilib packages for Slackware are provided by Eric, so you know they'll work with Wine. Good luck!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.