Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[Rene Janssen <rjanssen at ns dot oke dot nl>]

I agree that one should know what they are doing when updating manually to
glibc2. 
Why do you advice to build glibc2 with egcs-1.0.3? Is that safe enough? 
Maybe you should make your step by step guide also available through the
Glibc2 homepage, so we can
verify & track problems that occur when installing glibc manually.

Thanks.


At 11:07 AM 11/30/98 -0800, H.J. Lu wrote:
>
>Personally, I won't do it that way. It has so many problems. You have
>to know what you are doing. I suggest you get a new glibc 2 based system
>instead. I am running RedHat 5.2 now. I have no serious problem.
>
>I don't have the time to write things down in details. If you want to
>install glibc 2 under /usr, you can try
>
>1. Install my egcs-1.0.3-libc5.x86.tar.bz2.
>2. Configre glibc 2 with --prefix=/usr.
>3. Build/install glibc 2.
>4. Install my egcs-1.0.3-glibc.x86.tar.bz2.
>5. Remove all header files which are not overwritten by the
>header files from glibc 2.
>6. Add /usr/i486-linux-libc5/lib to /etc/ld.so.conf.
>7. Copy all the old shared libraries to /usr/i486-linux-libc5/lib,
>excluding those in /lib. 
>8. Run ldconfig.
>9. Remove all the old libraries, except for those in
>/usr/i486-linux-libc5/lib and /lib, with "rm -f".
>10. Remove the old lib*.so in /lib.
>11. Do
># sync
># sync
># sync
># sync
>and then push the reset button.
>12. Configure egcs as
># ...../configure --enable-shared --enable-threads --prefix=/usr
--with-local-prefix=/usr/local
>13. Build/install egcs.
>14. Recompile any libraries you want to use to build programs.
>
>Now you are done. You can recompile any programs to link against glibc 2.
>
>As I said, it is very tricky. You have to know what you are
>doing.
>
>
>H.J.
>
>