From owner-freebsd-stable@FreeBSD.ORG Tue Jun 28 22:05:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D36D16A41C for ; Tue, 28 Jun 2005 22:05:22 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B4B143D48 for ; Tue, 28 Jun 2005 22:05:21 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DnO5Y-0004u5-Kn for freebsd-stable@freebsd.org; Tue, 28 Jun 2005 23:57:52 +0200 Received: from gn-hgk-15cd4.adsl.wanadoo.nl ([81.69.122.212]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Jun 2005 23:57:52 +0200 Received: from A.S.Usov by gn-hgk-15cd4.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Jun 2005 23:57:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Alexander S. Usov" Date: Wed, 29 Jun 2005 00:04:23 +0200 Organization: KVI Lines: 45 Message-ID: References: <20050628154627.GJ40423@elvis.mu.org> <790a9fff05062809211c27a435@mail.gmail.com> <200506281844.07644.lofi@freebsd.org> <20050628182847.GB92486@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gn-hgk-15cd4.adsl.wanadoo.nl User-Agent: KNode/0.9.1 Sender: news Subject: Re: libstdc++ version bump. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2005 22:05:22 -0000 Alexander S. Usov wrote: > 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? I think I have to clarify my question a bit: I have a program which is a mix of c++ & fortran code. Fortran part is compiled with lang/ifc, so to link it I use something like ifort -o prog for_lib.a cpp_lib.a -l.... -lstdc++ Now I have to use one more library, which is not (yet) compatible with gcc 3.4 and up. If it matters -- this library is luabind (luabind.sf.net) and I don't really know of any alternatives to it (except tolua/tolua++ which are even more problematic). So to link my code now I have to rebuild a bunch of other packages using gcc33 and link it like that: ifort -o prog ...... /usr/local/lib/gcc-lib/......./libstdc++.a Doing it this way is quite messy, provided that I have to build/use this code time to time on linux machines where it should be linked in absolutely different way. So the question is if it possible to convince lang/gcc33 to produce code binary compatible with system-wide gcc 3.4? -- Best regards, Alexander.