This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Shared library annoyance with gcc-3_0-branch
On Mon, Feb 19, 2001 at 03:29:33PM -0800, Mark Mitchell wrote:
>
> My recommendation is not official, but here is what I think,
> personally:
>
> - The default behavior by the GCC driver is a good default.
> Distributors should leave it alone.
>
> - On a system where GCC is the primary compiler, libgcc_s.so
> should go in /lib, so that it is available to programs
> as soon as possible.
>
It is a good start. But it is a very bad idea to have
lrwxrwxrwx 1 hjl hjl 13 Feb 19 16:02 libgcc_s.so -> libgcc_s.so.0
-rw-r--r-- 1 hjl hjl 180260 Feb 19 04:14 libgcc_s.so.0
Please remember when you install/untar libgcc_s.so.0 like this, you may
overide an libgcc_s.so.0 which is being used other processes. One way
to get around it is to have something like
lrwxrwxrwx 1 hjl hjl 13 Feb 19 16:02 libgcc_s.so -> libgcc_s.so.0
lrwxrwxrwx 1 hjl hjl 13 Feb 19 16:02 libgcc_s.so.0 -> libgcc-3.0-20010219.so
-rw-r--r-- 1 hjl hjl 180260 Feb 19 04:14 libgcc-3.0-20010219.so
--
H.J. Lu (hjl@valinux.com)