From owner-freebsd-current@FreeBSD.ORG Fri Jul 30 18:13:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9B4316A4D0 for ; Fri, 30 Jul 2004 18:13:16 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49A0543D5A for ; Fri, 30 Jul 2004 18:13:16 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.100.95]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040730181255.IQIJ22385.out006.verizon.net@[192.168.1.3]>; Fri, 30 Jul 2004 13:12:55 -0500 Message-ID: <410A8FA5.4070008@mac.com> Date: Fri, 30 Jul 2004 14:12:53 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20040729144205.6ABEF5CA2@techpc04.okladot.state.ok.us> <20040729164738.523C85CA2@techpc04.okladot.state.ok.us> <20040729174420.GA9911@dan.emsphone.com> In-Reply-To: <20040729174420.GA9911@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [68.161.100.95] at Fri, 30 Jul 2004 13:12:55 -0500 cc: Dan Nelson cc: Paul Seniura Subject: Re: about the gcc 3.4.x problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 18:13:16 -0000 Dan Nelson wrote: [ ... ] > In general, C++ object files are not portable across different gcc releases, > since they fix ABI bugs in every release. Code built with 3.4 may not link > to an old 3.3 libstdc++, thus the dependency on the port's own libstdc++. I > don't see a problem here. I see a problem with C++ object files not being portable from release to release, but you're certainly right that it's not a new problem or one designed to bedevil Paul Seniura in particular. :-) I was going to suggest to Paul that if you run into problems when something changes, using cvsup and a date specification to track down the specific timeframe when something broke can be quite helpful. It also means that you can update back a few days (um, "backdate"?) to a system which was working until the problem gets fixed. However, I don't know whether CTM or whatever it was lets you do that. -- -Chuck PS: I suppose that asking why GCC keeps changing how it does C++ symbol name mangling ought to be discussed on a GCC forum, but considering that FreeBSD keeps a vendor branch, why don't the maintainers choose not import changes which break the C++ ABI into the FreeBSD version of GCC?