From owner-freebsd-current@FreeBSD.ORG Fri Jul 18 10:23:37 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 338F437B401 for ; Fri, 18 Jul 2003 10:23:37 -0700 (PDT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63D0043F3F for ; Fri, 18 Jul 2003 10:23:36 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id C117054840; Fri, 18 Jul 2003 12:23:35 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 5D5896D455; Fri, 18 Jul 2003 12:23:35 -0500 (CDT) Date: Fri, 18 Jul 2003 12:23:35 -0500 From: "Jacques A. Vidrine" To: Michael Nottebrock Message-ID: <20030718172335.GA70231@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Michael Nottebrock , Alexander Kabaev , freebsd-current@FreeBSD.org References: <1058366903.81198.18.camel@skeeve> <20030718153358.GC67855@madman.celabo.org> <20030718113753.080b442d.ak03@gte.com> <200307181812.18604.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307181812.18604.michaelnottebrock@gmx.net> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-current@FreeBSD.org Subject: Re: gcc-3.3 issues 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, 18 Jul 2003 17:23:37 -0000 [For some reason I haven't seen Alexander's post yet, so I'm mixing replies here.] On Fri, Jul 18, 2003 at 06:12:10PM +0200, Michael Nottebrock wrote: > On Friday 18 July 2003 17:37, Alexander Kabaev wrote: > > On Fri, 18 Jul 2003 10:33:58 -0500 > > > > "Jacques A. Vidrine" wrote: > > > I also recall lots of missing `typename's in the system headers that > > > were resolved in the actual GCC distribution. > > > > > > Alexander, do the STL headers et. al. get updated with the rest of the > > > compiler chain? > > > > Yes. But libstdc++ itself lags a bit behind GCC features. The reason why > > GCC ports are not reporting any errors is because by default GCC > > suppresses warnings from system headers, and C++ headers are considered > > system. We disable this suppression in imported compiler. Ah, that didn't occur to me. Duh. I guess we shall just wait for libstdc++ to catch up --- it looks like at least some of these issues are already fixed in GCC CVS. > I guess the next question is whether this is fixable, maybe even by enabling > said supression, at least for a short while. It seems the better fix than to > go and remove -pedantic from all the helloworlds that may linger in the > ports-tree. Even when libstdc++ is updated, we'll still be left with warnings from C-derived headers, such as the `long long' stuff. That should be fixable in some other fashion, but such discussion probably belongs on freebsd-standards@. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se