lib crazy

Mike Cantrell mikec@autodispatch.com
Wed, 26 Jul 2000 17:35:04 -0700


When you install new libraries, you have to make sure the path to the new
libraries is included in the /etc/ld.so.conf file and then run ldconfig (all
done as the root user of course). If you don't have root access (which you
should since your installing RPM's but just FYI), you can install the lib's
to your home dir, and set your LD_LIBRARY_PATH variable to include the lib
dir.

You can find out what dir the lib's were installed to by doing this:

rpm -qa|grep -i <package name>  # to get the correct package name
rpm -ql <package name found from above command>  #lists the files

Most packages should do this automatically but not all packages are created
equal :)

Hope it helps,
Mike Cantrell

> > > On Wed, 26 Jul 2000, you wrote:
> > > >
> > > > OK, this is probably a stupid newbie question.  Everytime I install
an
> > RPM on on my mandrake 7.1 system I seem to get some lib dependancy
error.
> > that is fine, I download the lib and install it.  However, after the lib
> > installation, I still get a dependancy error.  Do I have to do something
> > with my libs after I install them in order for them to be recognized?
For
> > instance, I installed libgtk+ and the Cheops rpm couldnt find it.  Is
there
> > something obvious here I am missing?  Thanks.
> > > >
> > > > - Joel