Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
assuming you are using red hat ( since that's what's in you're profile):
rpm -e glib-2 ( or may be named glib2 or something similar, it's NOT named glibc ( some people get this one confused, do not remove glibc))
when you install your new one, reinstall it to the same place ( on RH it should be /usr) and make a package of your build and install it instead of "make install", or upgrading/removal in the future will be a pain. if you don't know how to make rpm's, look into rpmbuild or checkinstall.
depends on what name you want, do you want the old glib that came with your install's name or the one you just installed?
you cannot do "rpm --xx" with anything you installed from source without making a rpm of the build. rpm keeps it own database, which is upgraded by rpm itself. it has no idea what you installed from source or where you installed it to. ( if you make rpm's of your builds, not only will it make it easier on you for removal/upgrade, it also upgrades the rpm database so it know's what you installed and where it is so the next time you attempt to install an rpm that needs glib-2.x, it know's that dependency is satisfied).
if you are removing the old one ( the one that came with the system) all you need to do is rpm -e <package name> and it will uninstall it ( you might have to pass the --force option to rpm, as alot of programs depend on glib).
If the glib you currently use is 1.2 then just keep it on there and install glib-2.0 alongside. They are totally seperate libraries and do not interfere with each other.
So many times on here people give answers that make the job so much more difficult than it has to be.
suppose the distro what you are running is redhat.
rpm -qa | grep glib
remove the feedback by rpm -qa with the command rpm -e
you must be ware of that if you removed older glib then any apps based on it will never be available for working.