Date: Tue, 28 Jun 2005 23:45:38 +0200 From: "Alexander S. Usov" <A.S.Usov@kvi.nl> To: freebsd-stable@freebsd.org Subject: Re: libstdc++ version bump. Message-ID: <d9sg0h$3ng$4@sea.gmane.org> References: <20050628154627.GJ40423@elvis.mu.org> <790a9fff05062809211c27a435@mail.gmail.com> <200506281844.07644.lofi@freebsd.org> <20050628182847.GB92486@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > On Tue, Jun 28, 2005 at 06:44:02PM +0200, Michael Nottebrock wrote: >> On Tuesday, 28. June 2005 18:21, Scot Hetzel wrote: >> >> > Are you sure that the problem is with libstdc++ and not the above >> > libraries? >> >> Yes, it's a well known-fact. In fact there might have been a break of ABI >> backwards-compatibility between gcc 3.3 and 3.4, too, but I'm not sure. > > There was. 3.3 could support either the C++ ABI of GCC 3.2, in which > there was an implementation bug; or the fixed ABI of 3.4. I had hoped we > had gone with the fixed ABI rather than being G++ 3.2 compatible, but > that is what users wanted at the time. Do I read it correctly that on 5.4 (with 3.4 in it) it is possible to convince lang/gcc33 to be binary compatible with system libraries? Do you have any link for it? -- Best regards, Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9sg0h$3ng$4>