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.
The new exiv2 actually supports WebP, but *not* libwebp. They've reinvented the wheel for some reason. Nevertheless, libwebp is becoming widely used so I'll look into that. Thanks.
[zakame:~] % command emacs --debug-init -nw
emacs: error while loading shared libraries: libMagickWand-6.Q16.so.4: cannot open shared object file: No such file or directory
[zakame:~] 127 % ldd /usr/bin/emacs | grep 'not found'
libMagickWand-6.Q16.so.4 => not found
libMagickCore-6.Q16.so.4 => not found
[zakame:~] %
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,120
Rep:
Quote:
Originally Posted by zakame
emacs needs a rebuild as well:
Code:
[zakame:~] % command emacs --debug-init -nw
emacs: error while loading shared libraries: libMagickWand-6.Q16.so.4: cannot open shared object file: No such file or directory
[zakame:~] 127 % ldd /usr/bin/emacs | grep 'not found'
libMagickWand-6.Q16.so.4 => not found
libMagickCore-6.Q16.so.4 => not found
[zakame:~] %
Done. That was fast!
Quote:
Wed Jul 19 20:58:46 UTC 2017
e/emacs-25.2-x86_64-2.txz: Rebuilt.
Linked against imagemagick-6.9.9-0.
l/gdk-pixbuf2-2.36.7-x86_64-1.txz: Upgraded.
l/gtk+3-3.22.17-x86_64-1.txz: Upgraded.
l/harfbuzz-1.4.7-x86_64-1.txz: Upgraded.
l/virtuoso-ose-6.1.8-x86_64-6.txz: Rebuilt.
Linked against imagemagick-6.9.9-0.
n/libgcrypt-1.8.0-x86_64-1.txz: Upgraded.
xap/xine-lib-1.2.8-x86_64-2.txz: Rebuilt.
Linked against imagemagick-6.9.9-0.
xap/xlockmore-5.54-x86_64-1.txz: Upgraded.
Linked against imagemagick-6.9.9-0.
+--------------------------+
My best guess is piterpunk, who gave us the slackpkg tool. The first time I ever upgraded my Slackware install, I conducted everything manually, as there was no other option. When slackpkg came along, I was amazed at how it handled everything so easily and cleanly. As for pushing, slackpkg resided in /extra through a number of releases before becoming part of official Slackware. The long gestation allowed for thorough examination of the then new tool.
If the lilo prompt now appears dated with the appearance of (and requirement for) newer boot loaders, it simply reflects the longstanding tradition of lilo being the official Slackware boot loader. If the prompt now peeves you, why not use the clever functionality that is provided within slackpkg? Simply copy /usr/libexec/slackpkg/functions.d/post-functions.sh to a new file that lexicographically sorts after the original, amend the lookkernel() function to suit your needs along the lines suggested by Loomx, then enjoy your local customisation. I have being doing this for years, so that I am automatically prompted to build a new initrd when required.
As a continuing user of lilo, I want the existing functionality retained.
I also appreciate that Slackware still gives a nod to past contributors to the open source community by retention of software that seems quaint and quirky to those without the history.
Perhaps this brief history might tone down some of the denigration from the nitpickers who have not given to Slackware what others have done in the past.
I hope you were biased by Darth Vader post, whose language is what it is.
Most of us is doing here what this thread is for.
And many of us contribute to Slackware this or the other way.
I've updated my Slackware 14.2 LLVM package to the one from -current (i.e. 4.0.1).
I also have libedit from SBo, at version 20170329_3.1 as opposed to libedit-20160903_3.1 that's found in -current.
This combination seems to be causing lldb to misbehave and spit out Unicode keycodes instead of the actual characters.
It turns out to be known problem. Sorry for not providing references, but you'll be able to find them when the time comes ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
