Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm trying to compile and install package "gnupg-2.0.4" on a RHEL 4.5 32bit x86 system. I have downloaded, successfully compiled and installed multiple prereq libraries including "libgcrypt 1.2.4". But when I try to compile gnupg it always aborts with a fatal error message "libgcrypt 1.2.0 too old need libgcrypt 1.2.2". When I run configure of gnupg before compile the return status of the libgcrypt check shows libgcrypt 1.2.4 was recognized. The gnupg configure process sees libgcrypt 1.2.4, but the gnupg compile process is only seeing an older down level version of libgcrypt. How do I make the gnupg compile process recognize and use the later level libgcrypt library I just installed?
I've seen some packages before just look at the RPM database for file/package information. If you've installed a library from source, it might not pick it up if the configure program or makefile is just checking the RPM. If there's a "configure" script, try running it with "--help", and it'll usually pop up a flag-list, which should tell you how to disable checking for that library, if you're sure you've got it installed.
I managed to resolve this one myself, so I'll document the fix here to make reading this thread useful to someone else with a similar problem.
The problem was that down level version 1.2.0 of the libgcrypt library was already present in /usr/lib and the install process for version 1.2.4 of the libgcrypt library that I built placed it in /usr/local/lib. Seems the gnupg configure check found the correct version of libgcrypt in /usr/local/lib but the gnupg compile process could only see the old version of libgcrypt in /usr/lib. Eliminating the old version of libgcrypt in /usr/lib fixed the compile fatal error.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.