This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the EGCS project.
Re: Building a shared libgcc
- To: Alexandre Oliva <oliva@dcc.unicamp.br>
- Subject: Re: Building a shared libgcc
- From: Jeffrey A Law <law@cygnus.com>
- Date: Mon, 02 Aug 1999 22:27:04 -0600
- cc: Richard Henderson <rth@cygnus.com>, gcc@gcc.gnu.org, libtool@gnu.org
- Reply-To: law@cygnus.com
In message <oremhlbipt.fsf@cupuacu.lsd.dcc.unicamp.br>you write:
> Wow! That's cool, but what are we going to do to ensure that
> libgcc.so is found at run-time?
It is one of the issues we will have to solve.
> One idea is to build libgcc (and the other run-time libs) with
> libtool, and arrange that (some subset or equivalent of) libtool is
> used to link with it.
I'd prefer not to have to fart around with libtool if we can help it; but
ultimately we might have to.
> Do you see any drawback in the patch for DU that arranges that libgcc
> is fully copied into libstdc++, besides the fact that it might
> introduce binary compatibility problems if it was to be reverted? If
> this is the only problem with it, we could install it forever, given
> that it doesn't introduce any problem, and it fixes an IMHO serious
> existing problem.
I don't want to mess with this. Please, let's not try to solve this problem,
because no matter what we do, it's wrong.
jeff