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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Firstly: I've never installed this package but knowing the general rules my advice is to use:
'./configure --prefix=/usr --disable-posix-threads'
which prepare the Makefile for installation in /usr/lib against /usr/local/lib
Normally ldconfig is done with make command (observe the output messages), but if not try run it manually.
But before above:
1. remove all the libmcrypt.* files from all /usr/lib/ and /usr/local/lib/ directories
2. remove the last line from /etc/ld.so.conf
thanks for the quick reply dorian33.
using /usr/lib as the ins directory is a good idea, however, the remainder of the lib's i need to intsall (mhash, mcrypt) call for the use of /usr/local/lib/lib name
This is also needed by mcrypt. The version I used was 0.8.17
1. tar -pxzf mhash-0.8.17.tar.gz
2. cd mhash-0.8.17
5. make install
6. ln -s /usr/local/lib/libmhash.so.2 /usr/lib/libmhash.so.2
7. cd ..
would using /usr/lib prefix affect the mhash ins?
As I wrote I don't know what the package contains, so all below is my experience.
I believe the '--prefix' is well documented. Try './configure --help'. You'll probably see that by default it is set to /usr/local. The "rest" part of the path should also be described over there. Usually for .so files it is "lib", for executables "bin", etc
As far as the "remainder" (as you call the mhash & mcrypt).
It is strange for me what you have written. Any "well written" application should:
- call another executable using $PATH variable rather than fixed directory
- use shared library using just its name rather than absolute path library location
You can put the .so files in any directory you want; the default are /lib and /usr/lib but adding for instance /mydir/ to the ld.so.conf you makes ldconfig to index also this directory and after that the executable should be able to use requested library without any problems.
If you have got for instance libxxx.so.6 file - it is the xxx library version 6. But the programs are not usually interested in version number. So you need to do the 'ln -s libxxx.so.6 libxxx.so'. This way ldconfig will index the "both" libraries with names .so & .so.6 making possible to use the library independently of the "calling name".
I don't think that the link you have posted is necessary.