From owner-freebsd-current@FreeBSD.ORG Thu Nov 6 09:18:34 2003 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 488CD16A4CE for ; Thu, 6 Nov 2003 09:18:34 -0800 (PST) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02B6843FFD for ; Thu, 6 Nov 2003 09:18:31 -0800 (PST) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) hA6HITfw047079; Thu, 6 Nov 2003 18:18:29 +0100 (CET) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id hA6HIOOj047078; Thu, 6 Nov 2003 18:18:24 +0100 (CET) (envelope-from marius) Date: Thu, 6 Nov 2003 18:18:24 +0100 From: Marius Strobl To: Alexander Kabaev Message-ID: <20031106181824.B55161@newtrinity.zeist.de> References: <200311061555.hA6Ft08H051563@www.kukulies.org> <20031106112828.7985100a.ak03@gte.com> <20031106174459.A55161@newtrinity.zeist.de> <20031106115112.50b53136.ak03@gte.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20031106115112.50b53136.ak03@gte.com>; from ak03@gte.com on Thu, Nov 06, 2003 at 11:51:12AM -0500 X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 6.22.0.1; VDF 6.22.0.30 cc: "C. Kukulies" cc: freebsd-current@freebsd.org Subject: Re: g++ problem 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: Thu, 06 Nov 2003 17:18:34 -0000 On Thu, Nov 06, 2003 at 11:51:12AM -0500, Alexander Kabaev wrote: > On Thu, 6 Nov 2003 17:44:59 +0100 > Marius Strobl wrote: > > > This happens with g++ 3.x ... > This will happen with g++ 3.x, 2.x, 1.x and future 4.x too. I.e. the > GCC is not at fault and the subject of the original message is > misleading. > It's at least not fatal with g++ 2.95.4 on 4-stable, that's what I meant. But yes, GCC is not at fault.