Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
01-22-2014, 12:57 AM
|
#1
|
Member
Registered: Dec 2011
Distribution: Mint, Slackware
Posts: 43
Rep:
|
Slackware 14, emacs won't launch, how to install missing library?
It appears I'm missing a shared library for Emacs. I'm trying to launch in terminal mode. When I try to launch I get this error:
Code:
$ emacs -nw
emacs: error while loading shared libraries: libMagickWand-6.Q16.so.1: cannot open shared object file: No such file or directory
I installed the X Windows package, but did not install the X Windows Apps package. I am coming from debian distros (Mint) so usually I go to the package manager for installing missing software.
How should I proceed with Slackware, to find and install missing or new software or libraries?
|
|
|
01-22-2014, 01:08 AM
|
#2
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
If you are new to Slackware it is strongly recommended to make a full install (even long-time Slackware users usually do that).
Assuming that you have configured the slackpkg package manager correctly you would first find out which package contains that library:
Code:
>>>slackpkg file-search libMagickWand
DONE
The list below shows the packages that contains "libMagickWand" file.
[ Status ] [ Repository ] [ Package ]
installed imagemagick-6.8.6_10-x86_64-1
You can search specific packages using "slackpkg search package".
Your output will look different, since I use the slackpkg+ plugin, but it will nonetheless report that the package you need is the imagemagick package. So just install that:
Code:
slackpkg install imagemagick
But again, it is strongly recommended that you make a standard full installation.
|
|
1 members found this post helpful.
|
01-22-2014, 01:11 AM
|
#3
|
LQ Guru
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,385
|
Slackware is offered as an all-in-one distribution, it doesn't have tools that manage dependencies resolution, that is left to the system administrator (you).
So you should opt to switch to a full installation (the only one supported), it's easy to do it with slackpkg:
- set a mirror in /etc/slackpkg/mirrors (the one corresponding to your version, 32 or 64bit)
- give the command
- then, if you're on 32bit slackware
Code:
slackpkg install slackware
if you are instead on 64bit slackware
Code:
slackpkg install slackware64
Last edited by ponce; 01-22-2014 at 01:13 AM.
|
|
1 members found this post helpful.
|
01-22-2014, 02:07 AM
|
#4
|
Member
Registered: Dec 2011
Distribution: Mint, Slackware
Posts: 43
Original Poster
Rep:
|
Okay, thank you for the quick reply.
Just curious, do the 'current' packages just point to 14.1 right now, or are they newer?
|
|
|
01-22-2014, 02:32 AM
|
#5
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
-current is the development version of Slackware.
|
|
1 members found this post helpful.
|
01-22-2014, 06:19 AM
|
#6
|
Member
Registered: May 2004
Distribution: BSD
Posts: 269
Rep:
|
From looking at the changelog, there were mostly security fixes in -current since 14.1 was released. Calligra was updated to 2.7.5, cairo rebuilt without specific options. and so on.
edit: Oh, and firefox was updated to the latest version (not ESR).
Last edited by lems; 01-22-2014 at 06:20 AM.
|
|
|
01-22-2014, 06:54 AM
|
#7
|
Senior Member
Registered: Mar 2007
Posts: 2,390
|
Quote:
Originally Posted by Tachtory
I'm trying to launch in terminal mode. When I try to launch I get this error:
Code:
$ emacs -nw
emacs: error while loading shared libraries: libMagickWand-6.Q16.so.1: cannot open shared object file: No such file or directory
|
The emacs package installs two versions of the emacs binary: emacs-24.3-with-x11 and emacs-24.3-no-x11. And it makes a symbolic link, so that command emacs starts emacs-24.3-with-x11 as default.
You could have fixed it by using the no-x11 version, instead. As root:
Code:
ln -sf emacs-24.3-no-x11 /usr/bin/emacs
(Or 24.2 in Slackware 14.0).
Last edited by Petri Kaukasoina; 01-22-2014 at 06:57 AM.
|
|
2 members found this post helpful.
|
01-22-2014, 07:59 AM
|
#8
|
Member
Registered: Dec 2011
Distribution: Mint, Slackware
Posts: 43
Original Poster
Rep:
|
That sounds good!
So if I'm really serious about learning emacs I could add this to my bashrc?
Code:
alias vim="emacs-24.3-no-x11"
|
|
|
01-22-2014, 09:05 AM
|
#9
|
Member
Registered: May 2004
Distribution: BSD
Posts: 269
Rep:
|
And don't forget to put
Code:
(setq viper-mode t)
(require 'viper)
into your ~/.emacs.
;-)
|
|
|
01-22-2014, 12:46 PM
|
#10
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Actually it's ~/.emacs.d/init.el these days.
|
|
2 members found this post helpful.
|
01-22-2014, 02:10 PM
|
#11
|
Member
Registered: May 2004
Distribution: BSD
Posts: 269
Rep:
|
Quote:
Originally Posted by Richard Cranium
Actually it's ~/.emacs.d/init.el these days.
|
Thanks, I did not know that. I tried emacs a few times and did not want to insult anyone. Both are powerful editors, in my opinion, it's just that I'm used to vi (I use nvi most of the time).
|
|
|
01-22-2014, 03:07 PM
|
#12
|
Member
Registered: Aug 2009
Location: Nijmegen, The Netherlands
Distribution: Slackware 14
Posts: 42
Rep:
|
Quote:
Originally Posted by lems
And don't forget to put
Code:
(setq viper-mode t)
(require 'viper)
into your ~/.emacs.
;-)
|
I think you want evil now iso viper
Marcel
|
|
|
01-22-2014, 06:45 PM
|
#13
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Quote:
Originally Posted by lems
Thanks, I did not know that. I tried emacs a few times and did not want to insult anyone. Both are powerful editors, in my opinion, it's just that I'm used to vi (I use nvi most of the time).
|
No sweat. It used to be ~/.emacs and that actually still works. But someday, it won't.
The fastest guy on the keyboard that I ever watched used emacs with vi keybindings. I always felt as if I should have a fire extinguisher near when I watched him type. It was mind-boggling.
Last edited by Richard Cranium; 01-22-2014 at 06:47 PM.
|
|
|
All times are GMT -5. The time now is 06:21 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|