This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
On Thu, 18 Feb 1999, Santos Halpar wrote:
>nbecker@fred.net wrote:
>> I'm going to try building 1.1.2 on my glibc2.0.7/egcs-1.1.1 system.
>> I will then build glibc-2.1. I think I need to now rebuild
>> libstdc++-2.9, right?
>
>That's what the rumor around the campfire is. I'd rebuild libstdc++
>after installing glibc-2.1.
>
>> I will then try installing glibc-2.1 and (assuming I'm not dead yet)
>> see if the binaries still work.
>>
>> If glibc-2.1 install breaks everything, is there an easier way to
>> remove it, other than restore everything from tape?
>
>Been there, done that -- one of the 2.1 betas failed to function for
>me. Thankfully, I had copied the previous contents of /lib over to
>another partition and had saved an "ls -al" of /lib to ensure I knew
>where the symlinks had to point (ldconfig is statically linked on my
>system, but it's nice to have a sanity check).
I perhaps have done something slightly more difficult:
upgraded to glibc-2.1 directly from libc-5.4.46.
- I downloaded glibc2 binaries of X11, Netscape;
- rebuilt egcs-2.91.60.1 19990115/Linux (egcs-1.1.1 release).
- rebuilt ncurses
- rebuilt Qt-1.42, KDE-1.1, groff and many other packages (the Linux
distribution were Slackware-3.6)
I currently don't see reason to return back, but it's very common that packages
needs hacking to be built with glibc-2.1 and 2.2.X kernels.
So today I found that ftpd does not work. So I rebuilt latest version but
I needed to patch it in one place to get it built at all. (Possible workaround
for many problems is -D__NO_STRING_INLINES)
Andris