bgodden
asked on
Installing/upgrading glib, gtk and gimp
Hi,
Finally got RH 6.0 installed (thanks to help form folks on this site :-) and now I'm trying to add the latest gimp. It needs the latest gtk which needs the latest glib... The versions I want to intall are the latest stable (gimp 1.0.4, gtk+ 1.2.7, glib 1.2.7).
Currently the system appears to have gtk 1.2.1 and glib 1.2.1.
The part of having trouble with is how to understand how to prepare for these upgrades. It looked like glib worked fine through configure, make and make install, but when I try to go to the next step, gtk, it complains that it needs glib 1.2.7.
I'm assuming I need to clean out all previous versions before going through these steps? When I search for this stuff it looks like there's quite a bit and I don't want to remove anything I don't understand to be removing, etc. Are there methods to do clean-up before an upgrade? I would really like to know general methods as well as it will be good to know for future stuff.
Any tips on this would be greatly appreciated!
Thanks.
Finally got RH 6.0 installed (thanks to help form folks on this site :-) and now I'm trying to add the latest gimp. It needs the latest gtk which needs the latest glib... The versions I want to intall are the latest stable (gimp 1.0.4, gtk+ 1.2.7, glib 1.2.7).
Currently the system appears to have gtk 1.2.1 and glib 1.2.1.
The part of having trouble with is how to understand how to prepare for these upgrades. It looked like glib worked fine through configure, make and make install, but when I try to go to the next step, gtk, it complains that it needs glib 1.2.7.
I'm assuming I need to clean out all previous versions before going through these steps? When I search for this stuff it looks like there's quite a bit and I don't want to remove anything I don't understand to be removing, etc. Are there methods to do clean-up before an upgrade? I would really like to know general methods as well as it will be good to know for future stuff.
Any tips on this would be greatly appreciated!
Thanks.
ASKER
My friend jlevie :-)
Right ldconfig, I did see instruction for this... Doh! I didn't think about impact on evertything else and was eventiually planning on upgrading to 6.1, I suppose I should start from the ground up yes?
Looks like the web pages are good on doing this over the net. Any gotchas that come to mind before I proceed?
Thanks much.
-Brian
Right ldconfig, I did see instruction for this... Doh! I didn't think about impact on evertything else and was eventiually planning on upgrading to 6.1, I suppose I should start from the ground up yes?
Looks like the web pages are good on doing this over the net. Any gotchas that come to mind before I proceed?
Thanks much.
-Brian
I can't think of any offhand, especially in the case of a system that has been recently installed. The usual caveat applies about backing up data that you wouldn't want to lose if something went wrong.
I don't understand. Install, configure, removing? All by hand? Esspecially removing rpm based installs by hand? You don't seem to have been introduced to the advantages of RedHat's RPM.
Why don't you get yourself over to http://rufus.w3.org/linux/RPM/GByName.html and pick the latest binary RPM's suitable for your system.
Then back home you upgrade by doing a simple
rpm -U glib-1.2.7-1.i386.rpm
rpm -U gtk+-1.2.7-1.i386.rpm
rpm -U gimp-1.0.4-7.i386.rpm
That's all. Oh yeah, go see the rpm manpage.
Why don't you get yourself over to http://rufus.w3.org/linux/RPM/GByName.html and pick the latest binary RPM's suitable for your system.
Then back home you upgrade by doing a simple
rpm -U glib-1.2.7-1.i386.rpm
rpm -U gtk+-1.2.7-1.i386.rpm
rpm -U gimp-1.0.4-7.i386.rpm
That's all. Oh yeah, go see the rpm manpage.
ASKER
OK,
First, thanks for the pointer to the very useful resource.
I'm still thinking, though, that's it's probably a good idea to follow jlevie's logic in a case like this, where I would be upgrading glib and that this might have an effect on many different programs that are linked to the older libs. Seems like in a particular case such as this, it's best to do an all around upgrade and not have things break ongoing...
Counter-point?
First, thanks for the pointer to the very useful resource.
I'm still thinking, though, that's it's probably a good idea to follow jlevie's logic in a case like this, where I would be upgrading glib and that this might have an effect on many different programs that are linked to the older libs. Seems like in a particular case such as this, it's best to do an all around upgrade and not have things break ongoing...
Counter-point?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes. Aggreed. I was alluding to the same thing. Thanks for the help
While it can be done, upgrading libc on a system can get a bit dicey. Virtually everything on Linux uses the shared libc library. And they were built and tested against the older version. Even minor differences in the two libc's can have serious affects on the system's operation and stability.
Did you run ldconfig after installing the new libraries to rebuild the cache? See "man ldconfig" for details.