On Saturday 03 March 2001 17:32, you wrote:
Quoting Michael Perry on Sat, Mar 03, 2001 at 03:25:27PM -0800:
You could take the tar version and use the configure script to see what libraries it looks for or wants or capture the results of the ./configure to a logfile and see what it looks for. It may be a "newer library problem". I used to have this problem with my builds of gnome before SuSE and Gnome came together on the naming sequences of gnome packages. Then a gnome application would "expect glib.xxx.xxx.x". If it found something else, it would probably run but it would start acting wierd or eating memory when I closed it down. I stopped using a few programs (games especially) in gnome back then because I could not track the issues down. If I backcycled the library to something which appeared closer then some gnome core stuff would complain. Luckily, I had backed up the build a few times when I saw this happening so recovery was a bit easier. I also had a "junk install" of SuSE which I played with and tried different things on. When SuSE and gnome came together on package naming, things became much easier.
I don't mess anymore with kde or gnome, but I would suspect that there is a library incompatability which you have found. Try trapping what the configure or make programs do and see if you spot something suspect like a rather significant change in libraries from what the program wants to what you have.
I would also check on google for others which may have had this problem in the past with other applications.
One other thing that occurs to me is that you could use rpm itself to find out what applications/libraries, etc are dependencies for the program in question.
YOu could use some of the rpm metadata commands and check out what is required or what the package needs to operate correctly. We used to start with "rpm -qi nameofpackage.rpm" and start from there. That gives a good amount of info about the baseline capabilities of the package.
Then you could go on with some more detailed rpm commands like "rpm -qR nameofpackage.rpm". This command provides:
-R, --requires List packages on which this package depends.
I got most of these awhile ago from Maximum RPM but they are also explained in the rpm man pages.
Ya. Using sux -x in an xterm and running kpackage will show you the dependencies, which are all satisfied, obviously. I still think it is a base library incompatibility. JLK