This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A completely different approach to EH runtime
On Wed, Feb 21, 2001 at 11:34:24PM -0800, Zack Weinberg wrote:
> > now you have replaced a system library in /lib. Even if you use -rpath,
> > which I don't like, it will means all DSOs, including those come with
> > the system, opened by the new binary will use the new libgcc_s.so in
> > /path/to/other/lib. Do you think it is safe to do so? If yes, why not
> > put the new libgcc_s.so in /lib?
>
> The hard-line statement is: if it isn't safe, that is a bug.
>
> However, there are degrees of perceived safety. I might feel
> comfortable running my entire account with the new libgcc_s.so, but
> not comfortable causing the system daemons to use it too. I might
> have set up a special sandboxed user for test purposes.
>
> Also consider the case of an unprivileged user installing gcc in their
> own account. They don't put it in /lib because they can't.
>
Again, it is the same as 2 libc.so. I, as a glibc developer, don't want
to support it and I won't recommend it to other people.
--
H.J. Lu (hjl@valinux.com)