basslake wrote:
Hello I would like to upgrade SuSE70 glibc 2.1 to 2.2 . Then if glibc 2.1 binaries work with glibc 2.2 , would I still have a large number of binaries,or applications that are looking for links to the older libraries ?
I believe that when you install it there will be symlinks from the old to the new if the names have changed. I had no problems with this. I assume you are doing it from the vanilla glibc-2.2.x sources and not an rpm from somewhere.
I had problems with kvirc when I tried shared libraries package 71 from suse-ftp, (couldn't find libstdc++ something ) I accidently mis-took it for the update suggested in the kernel Changes file . )
Don't upgrade using an rpm. Use the sources.
I suppose I could upgrade to the newer KDE as well, along with glibc 2.2 . But it's really the binaries behind the scenes , running processes, system dependent, and other important scripts, or whatever, which I worry about causing unecessary problems . am I being too paranoid , or what ?
No, you should be a little paranoid about upgrading glibc as a mistake can leave you with no working system.
New Kernels, [2.4.4-series] also suggest upgrading to glibc 2.2 . This is my main reason for upgrading, and I also need gcc 2.95.3 which requires glibc2.2 .
You only need glibc-2.2.x for gcc 2.95.3 if you install it from the suse rpm. You can get the sources and configure/compile/install it for glibc-2.1 if you want.
So Is ti too much to fuss with at this time ?
Maybe, if all you need is gcc 2.95.3. I wouldn't upgrade glibc just for that. Like I said you can go and get the sources for gcc and install it on your glibc-2.1 system.
if not I would appreciate any suggestions, warnings, and advice Thanks JohnWM
Be cautious.. Mark