[PATCH] automated demangling styles list.

Marc Espie espie@quatramaran.ens.fr
Sat Jun 15 19:07:00 GMT 2002


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.

We also are fairly happy that we can manage to compile libiberty just
once, not once for binutils and once for gcc (even though this means
a bit of hackery is needed to keep pieces synch'ed).

Actually, I am prepared to deal with API changes in libiberty.

But, hey, just because linux with H.J.Lu's toolchain doesn't do it 
doesn't mean it doesn't exist.



More information about the Gcc mailing list