This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] automated demangling styles list.
- From: "H . J . Lu" <hjl at lucon dot org>
- To: Marc Espie <espie at quatramaran dot ens dot fr>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 15 Jun 2002 22:25:10 -0700
- Subject: Re: [PATCH] automated demangling styles list.
- References: <200206160104.g5G14Z725432@quatramaran.ens.fr>
On Sun, Jun 16, 2002 at 03:04:35AM +0200, Marc Espie wrote:
> In article <20020612170112.C8551@lucon.org> you write:
> >On Wed, Jun 12, 2002 at 07:56:38PM -0400, DJ Delorie wrote:
> >>
> >> > It is never meent to be binary compatible. It is compatible at the
> >> > source code level. The rest of my change depends on those changes.
> >> > What is the binary compatibility for?
>
> >> In case libiberty is installed as a shared library. If there's a
> >> binary incompatibility, then you can't install gcc and binutils at the
> >> same time.
>
> >I didn't know libiberty could be installed as a shared library. It is
> >never built/installed as a shared library under Linux even when
> >--enable-shared is used. If it is the case, it should be fixed or
> >dealt with, similar to libbfd.
>
> There is a world beyond linux yet, fortunately.
>
> OpenBSD, for one, does install libiberty as a shared library.
>
I was talking about the unmodified libiberty from the FSF. I don't
see anything in libiberty which builds a shared library on OpenBSD.
I must have missed something.
H.J.