LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (http://www.linuxquestions.org/questions/mandriva-30/)
-   -   RPM installer not recognizing installed libs? (http://www.linuxquestions.org/questions/mandriva-30/rpm-installer-not-recognizing-installed-libs-97554/)

Jiawen 09-27-2003 02:09 PM

RPM installer not recognizing installed libs?
 
I'm having trouble installing SCIM (a Chinese input system). I think I've fulfilled all the depencies, but every time I time I try "rpm -Uvh scim-0.8.1-1.i586.rpm", I get an error:
Quote:

error: failed dependencies:
gtk2 >= 2.2.0 is needed by scim-0.8.1-1
I have gtk+2.2.1 installed, however. I also tried installing an earlier version of SCIM that required gtk 2.0 or greater, but it then told me that I didn't have that installed, either.

Is the rpm installer not recognizing my gtk? Am I confused about what gtk is? Is it possible there's something wrong with SCIM? Or is it something else?

Thanks in advance for any help...

quatsch 09-28-2003 11:37 PM

the problem might be that the rpm is not built for mandrake. Go to rpmfind.net and look for a mandrake specific rpm. Maybe there is one.
You could also try using
urpmi scim-***
and see if that helps. Also
rpm --nodeps scim-***
might do it too.

If nothing else, you could get the source code and compile it yourself.


I

Jiawen 09-29-2003 11:24 AM

Thanks for the response, quatsch! You've been so helpful...

A search of rpmfind.net turned up no rpm's of scim at all. rpm --nodeps sounds kind of dangerous -- is there a danger of screwing up my system by doing that?

Finally, the ultimate newbie question -- how do I compile from source?

Thanks, as before, for any help you can give!

quatsch 09-29-2003 11:46 AM

I don't think it will screw your system if you install with it --nodeps. It just might not run. The really dangerous thing to do is to *un*install something with --nodeps because other programs might need it.

As for compiling, if you want to try it, you should get the source file - usually a tar.gz file - and unpack it first. There usually are brief instructions in the source files (usually named install and/or readme). You will have to install some devel packages but i think you can figure out which ones by looking at the error messages you get when trying to compile.

Jiawen 09-29-2003 12:55 PM

Excellent reply! Thanks again.

I think I'll avoid rpm --nodeps, if compiling from source is what you said. I thought it was some huge thing, but I've actually done it before.

The problem with GTK+ 2.2.1 not being recognized was within rpm, right? So if I do a source compile, it won't be a problem? Or was the unrecognized GTK+ from within the program itself?

Thanks again for any help you can give!

quatsch 09-29-2003 04:34 PM

I think there will be a config file in the source file that you might have to edit a bit to let it know where gtk is installed. If you try to compile it and it can't find something it needs, it will complain so you will know. With gtk+ the potential issue that it doesn't know the right path (you can find which file is installed where by the rpm by showing the full information in rpmdrake).


All times are GMT -5. The time now is 04:24 PM.