Part of the design for shared libraries includes the ability to have different versions exist on a machine and have the proper one be used. If you take a look in /usr/lib, you'll see lots of version numbers in the library names. So, by theory and design one should be able to have glibc-2.1.3 and glibc-2.2.0 coexist on a machine without trouble.
Note the above statements appear to be theory and design. They are not necessarily fact. At least twice I have installed a new version of glibc, only to discover that basic commands like "ls" no longer work because the want the _old_ version of glibc. The only safe way I know of upgrading glibc is to boot from the installation CDs and do a system upgrade. David In 07:25 PM 5/29/02, you wrote: >"Alfredo C.Lopez" wrote: > > > > Hi ! > > > > I have a cluster of machines running Linux Mandrake 7.1 with the necesary > > upgrades to run KDE 2 (installed in /opt/kde2 and coexist with the very old > > kde1). > > I make some upgrades without touching glibc (almost). This are the glibc > > packages I have installed: > > > > glibc-profile-2.1.3-18.3mdk > > glibc-devel-2.1.3-18.3mdk > > glibc-2.1.3-18.3mdk > > compat-glibc-5.3-2.0.7.9mdk > > > > I need to upgrade glibc from version 2.1.3 to version 2.2.x so I can > run the > > new intel fortran(and c++) compiler( and may be to run kde 3 and other > stuff > > :) ). > > I try to make the upgrade some time ago.... but I had to unmade the > > changes because the system experience problems like random errors.. > > I googled and find out that is common to have problems when you upgrade > > glibc. The other problem is that you need to reboot the machine to make the > > upgrade (but I think this can' t be solved). > > A couple of months ago it wasn't a problem ( I could find software for > > mandrake compiled for the old glibc or I could recompile it in my > system) but > > right now that's not posible anymore. > > More and more software need the new glibc. > > > > It's posible to keep the version of glibc and install the new one (may > be in > > other directory) and have both of them... may be with some magic :) ?. > > Any comment is appreciate. > > > >Hmmm, I am not sure but it is a good question. I do know, however, that >it is nearly impossible to upgrade a mandrake system from GLIBC 2.1.x to >GLIBC 2.2.x without breaking most everything in the system, and >consequently engendering suicidal ideation. My experience, and gut, >tells me you could *not* have two different sets of GLIBC. The GLIBC >program, being the basic libraries for just about everything you do in >mandrake, involves too much interaction with the environment, creating, >as I understand it, a complicated mix with such standards as locale, >POSIX settings, environment variables, etc. You mess with this stuff, >and you will probably live to regret it. > >But it would be great to hear from some programmers (any coders out >there?) about this. I will add, however, that your question belongs on >this list, and it most definitely falls within the purview of "expert". >My hunch is that you can not do this, Afl > >drjung >-- >J. Craig Woods >UNIX/NT Network/System Administration >http://www.trismegistus.net/resume.html >Character is built upon the debris of despair --Emerson > >Want to buy your Pack or Services from MandrakeSoft? >Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
