A completely different approach to EH runtime

[H . J . Lu]

On Thu, Feb 22, 2001 at 09:26:17AM -0800, Joe Buck wrote:
> 
> > 2. Only the new libgcc is visible to ld.so.
> 
> Because dynamic linking may have subtle differences on different systems,
> we will perhaps need OS-specific instructions to make sure that this is
> the case.  On SVR4-like systems, having the new libgcc be the first match
> in LD_LIBRARY_PATH should suffice.
> 
 
That is only true for non-suid programs. But even with LD_LIBRARY_PATH
there are several problems. One of them is all the programs you run
will use that libgcc. It should be ok for the binaries compiled with
the gcc you built. But it may not be ok for the system binaries
compiled with a different gcc. As I said many times, you don't want to
have more than one libc.so or libgcc_s.so on your machine. Having only
one libc.so/libgcc_s.so makes all those problem to go away.

You are entering a territory you have never been in before. Please
listen to people who have been there before. When Ulrich and I said it
wouldn't work, it is most likely to be true. I may even have missed
some other problems with 2 libc.so or libgcc_s.so.


-- 
H.J. Lu (hjl@valinux.com)