Different rpms may look for dependencies in different areas. Check you
/usr/lib and see if the library is there. Sometimes the rpm are looking
for a slightly older lib or one named a little differently. In this case
try doing a soft link to the lib name that the rpm is looking for during
install.
I am sure JLF will simply say this is more evidence as to why one should
use debian and apt-get (he already converted me).
Jason
On Wed, 26 Jul 2000,
joel@silverw.com (Joel Dudley) wrote:
> Date: Wed, 26 Jul 2000 15:09:35 -0700
> To: <Plug-discuss@lists.PLUG.phoenix.az.us>
> From: joel@silverw.com (Joel Dudley)
> Reply-To: plug-discuss@lists.PLUG.phoenix.az.us
> Subject: lib crazy
>
> 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
>
----------------------------------------------------------------------------
> "For the scientist who has lived by his faith in the power of reason, the
> story ends like a bad dream. He has scaled the mountains of ignorance; he
> is
> about to conquer the highest peak; as he pulls himself over the final
> rock,
> he is greeted by a band of theologians who have been sitting there for
> centuries."
>
> - Dr. Robert Jastrow
> Founder of NASA"s Goddard Institute for space studies
>
>
>
>
(text/plain)