libssh2 failed to compile complaining missing libgcrypt
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.
libssh2 failed to compile complaining missing libgcrypt
Hi All,
I have been trying to compile libssh2 on my slackware 4.1, but the configure always fails saying:
checking for libgcrypt... no
configure: error: cannot find OpenSSL or Libgcrypt,
try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH
I have installed both the OpenSSL and libgcrypt packages from the installation CD of slackware 4.1. but still I got this problem.
I did some research and found other people got similar problem on other distros (RH and Debian) and the solution is for them to install the devel package of the libgcrypt or openssl.
In Slackware the headers and source codes of the package are already included in the package. So what am I missing here ?
Thanks
Note: I have also tried to use the slackbuild script from the slackbuilds.org but the problem is exactly the same.
libssh2 has no additional requirements beyond a full install of Slackware. Did you do a full install of Slackware? If not, you are missing libraries. libgcrypt is its own package, and from your output, it looks like it isn't installed.
Hi thanks for the quick reply. yes sorry for the typo. It is actually 14.1 version (don't know why I forget to put the leading 1 twice). And it was the 32 bit version of slackware 14.1. Below is the snippet of my /var/log/packages. The libgcrypt and openssl are clearly there. and no if you mean by full install is I installed everything in the slackware CDs. I only install the packages that I think I need. I use xfce for instance instead of KDE. The question is which packet that is missing for the libssh2 to compile correctly ? Thanks
Hi thanks for the quick reply. yes sorry for the typo. It is actually 14.1 version (don't know why I forget to put the leading 1 twice). And it was the 32 bit version of slackware 14.1. Below is the snippet of my /var/log/packages. The libgcrypt and openssl are clearly there. and no if you mean by full install is I installed everything in the slackware CDs. I only install the packages that I think I need. I use xfce for instance instead of KDE. The question is which packet that is missing for the libssh2 to compile correctly ? Thanks
You need more packages. Looking at /var/log/packages/libgcrypt-1.6.3-x86_64-1, you can see it provides lib64/libgcrypt.so.20.0.3. If you now run 'ldd /lib64/libgcrypt.so.20.0.3', you should see somthing like:
My guess, from your snippet of installed packages, is that your output will say that libgpg-error.so.0 is not found. You should install the libgpg-error-1.18-x86_64-2 package (of coursed 32bit version in your case).
Issues like these are why it is typically recommended to do a full install of Slackware. Since Slackware doesn't come with any sort of dependency resolution, it is hard to know if what you have installed has all required dependencies for it to work, as you obviously saw here. Unless you are severely limited on space, there is no reason to not do a full install. Any programs installed, but not used, will not be started up, so it won't take any more resources than a small chunk of hard drive space. And with how cheap and large hard drives are, it is small enough most wouldn't notice.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.