Re: Libstdc++ versioning issues

John David Anglin wrote: >>AFAICS, there are no problems whatsover, because version 3.4.5 is *new* >>in 4.0.1. >> >> >See . This is >also . > >This is probably a bug in binutils but I d

Re: Libstdc++ versioning issues

> AFAICS, there are no problems whatsover, because version 3.4.5 is *new* > in 4.0.1. See . This is also . This is probably a bug in binutils but I don't have a warm fuzzy feeling about th

Re: Libstdc++ versioning issues

Mike Hearn wrote: >Are the new symbols new APIs, or will pre-existing code compiled with GCC >3.4.5 depend on these symbols when they would not have done when compiled >with GCC 3.4.0? > > AFAICS, there are no problems whatsover, because version 3.4.5 is *new* in 4.0.1. Paolo.

Re: Libstdc++ versioning issues

On Sun, 19 Jun 2005 15:06:58 +0200, Paolo Carlini wrote: > The issue that Benjamin just fixed is very simple to explain (much less > to fix ;) : some recently added exported symbols had the default v6 > version, that is, 3.4.0, instead of 3.4.5. Ah I see :) Are the new symbols new APIs, or will

Re: Libstdc++ versioning issues

Mike Hearn wrote: >On Tue, 14 Jun 2005 20:24:40 -0500, Benjamin Kosnik wrote: > > >>I'm testing a patch that resolves the issue. I expect to have additional >>details within 24 hrs, and will let you know details. >> >> >Is this bug #21405, or some other versioning issue? > > The issue that

Re: Libstdc++ versioning issues

On Tue, 14 Jun 2005 20:24:40 -0500, Benjamin Kosnik wrote: > I'm testing a patch that resolves the issue. I expect to have additional > details within 24 hrs, and will let you know details. Is this bug #21405, or some other versioning issue? thanks -mike

Re: Libstdc++ versioning issues

> What is an ETA for additional information? Am I correct in > understanding, from your previous mail, that these problems occurred in > 4.0.0 as well? Hi Mark. Thanks for your patience. I'm testing a patch that resolves the issue. I expect to have additional details within 24 hrs, and will l

Libstdc++ versioning issues

Benjamin -- Right now, the libstdc++ versioning/ABI situation is is all that stands between us and 4.0.1 RC2, now that Jakub has fixed the GLIBC miscompilation. What is an ETA for additional information? Am I correct in understanding, from your previous mail, that these problems occurred in