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.
Yes this is a full install of Slackware64 14.2, with AlienBob's multilib and WINE packages. I also have installed libvirt and virt-manager.
I believe there is an issue with which still hasn't been answered. libreadline.so.7 is a product of Readline 7.0 which is only available on the current branch of Slackware. libreadline in a stable 14.2 only uses readline 6.3. In going back through the build log's the request for libreadline.so.7 is needed by /usr/lib64/lua.so and it suggest using -rpath or -rpath-link. Also needed by liblua.so are libhistory.so.7, libncurses.so.6 and libtinfo.so.6 which are also not part of stable. So I'm wondering what package is missing or might need to be rebuilt? Or maybe there is a problem with this installation where a build tool has been lost or corrupted (although other packages build without issue). Slackpkg upgrade-all has been regularly run, so that should not be an issue. Perhaps just lua (version 5.1.5) needs to be rebuilt? Or is this an issue with OpenJRE-8u144 and the real jdk/jre needs to be installed?
If you have something that is referring to these non-existent libraries on your system, the simple explanation is you accidentally installed something that was meant for -current and not 14.2 (simple, but it doesn't mean this is actually the case -- just the first place to look). But to figure out what package that is might be a lot of work. First thing I'd do is check your 3rd-party pre-compiled packages, possibly from Eric (Alien Bob). If you accidentally grabbed one of his -current packages and installed that, it could be causing all your problems.
Boris Faure announced the following on the Enlightenment-users mailing list:
Quote:
Hello fellow Terminology enthusiasts!
I am pleased to release Terminology 1.1.1!
This release introduces the following changes:
Additions:
- Danish translation
Fixes:
- Fix issues with bottom margins
- No longer add spurious newlines in selections in the backlog
- No longer add space when running command from -e option
- Fix -T option to set the title of the window
Thank you for the feedback. I've checked all the 3rd party packages and have not found a -current version build. Attempting a re-build of all the dependencies has not resolved the failure or references.
I am wondering if instead I've hit an issue with the build of slackENLIGHTENMENT and its dependency SBo packages not being multilib aware.
To test this I'm going to re-evaluate if my ESET Nod32 for Linux can execute without 32 bit libraries (although they had to be present for the installation). If it is NOT required then I'll remove multilib and try this again. If it is required then I'll give more thought to the multilib impact on the lua and other dependency builds, since SBo FAQ talks to the issue of the correct library referencing.
I did not apply that correction to the deps, or were you asking if I had opened slackENLIGHTENEMNT and added to each of those slackbuilds?
I am aware of that FAQ and what I'd have to do is to open each slackbuild for slackENLIGHTENMENT and add those references. When I contemplated which slackbuilds required that change I realized that I don't know which SBo packages actually require the change and which don't, i.e. which are package building impactful and which are not. The GCC and GLIB files are already multilib from Alien Bob.
Or are you suggesting that every SBo package I ever build should have that correction? My understanding was that only certain packages that won't build need that correcting entry.
I did not apply that correction to the deps, or were you asking if I had opened slackENLIGHTENEMNT and added to each of those slackbuilds?
I am aware of that FAQ and what I'd have to do is to open each slackbuild for slackENLIGHTENMENT and add those references. When I contemplated which slackbuilds required that change I realized that I don't know which SBo packages actually require the change and which don't, i.e. which are package building impactful and which are not. The GCC and GLIB files are already multilib from Alien Bob.
Or are you suggesting that every SBo package I ever build should have that correction? My understanding was that only certain packages that won't build need that correcting entry.
I would start with just adding it to the deps for slackENLIGHTENMENT that are installed with `sbopkg`. I always ran multilib and never had the error you mention.
Interesting, did not know about that one. What is different about it than slackENLIGHTENMENT?
Looks like it has a few more packages ... are there build changes? I see they are hard coding the MAKEFLAGS ... that's never a good idea unless you need to code `-j1` because of a build fail, but they have `-j5`, that won't necessarily work on all systems.
Interesting, did not know about that one. What is different about it than slackENLIGHTENMENT?
Looks like it has a few more packages ... are there build changes? I see they are hard coding the MAKEFLAGS ... that's never a good idea unless you need to code `-j1` because of a build fail, but they have `-j5`, that won't necessarily work on all systems.
I did this in 2015, after that i never looked again. Whether it's alike or not, i do not know, im sorry.
About -j5 i will remove later, like others .slackbuilds i have. Thanks for remember :-)
At the time I did i wanted all dependencies together with the build i think have some flags differents inside efl too
Last edited by Candelabrus; 09-07-2017 at 01:07 PM.
I was about to answer something like "Hey, just have a look in the archive, or consult the enlightenment.org website, or ask them, this is a Slackware forum!"
But as your question gave me the occasion to find this little gem: https://www.enlightenment.org/docs/c/start that will help me begin to learn C, I'll just say: Thanks!
I was about to answer something like "Hey, just have a look in the archive, or consult the enlightenment.org website, or ask them, this is a Slackware forum!"
But as your question gave me the occasion to find this little gem: https://www.enlightenment.org/docs/c/start that will help me begin to learn C, I'll just say: Thanks!
Cool, i did one happy today :-)
About extra
Quote:
Extra is a app which allows you to install elementary themes on your computer
The app is based on elementary and uses efl libraries to download the theme.
It does so by fetching themes from extra.enlightenment.org.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.