From owner-freebsd-current@FreeBSD.ORG Thu Jul 17 13:50:16 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 5879837B401; Thu, 17 Jul 2003 13:50:16 -0700 (PDT) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 636F643F75; Thu, 17 Jul 2003 13:50:15 -0700 (PDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (250-217.customer.cloud9.net [168.100.250.217])h6HKoC7G069128 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Thu, 17 Jul 2003 16:50:13 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Alexander Kabaev , Michael Nottebrock Date: Thu, 17 Jul 2003 16:50:15 -0400 User-Agent: KMail/1.5.1 References: <1058366903.81198.18.camel@skeeve> <200307172218.39124.michaelnottebrock@gmx.net> <20030717162554.680475cc.ak03@gte.com> In-Reply-To: <20030717162554.680475cc.ak03@gte.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307171650.15405@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org cc: kde@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: Thu, 17 Jul 2003 20:50:16 -0000 On Thu, 17 Jul 2003 22:18:38 +0200 Michael Nottebrock wrote: => On Thursday 17 July 2003 22:11, Alexander Kabaev wrote: => => > -Werror? As doctor said: if it hurts, DON'T DO THAT. => => In the kdelibs case, it's definitely _not_ -Werror =Whatever it is, I haven't seen one shred of evidence of "GCC issues" in =your messages, just complaints. Just an example: bad code generated is =GCC issue, more strict C++ compliance requirements - not. So what of =these two did you mean? Hi, Alexander! First of all, thank you very much for integrating the new GCC into FreeBSD. The pentium4-specific fixes and optimizations, as well as other compiler's features and improvements are much appreciated. Here is how to reproduce the problem, Michael is talking about. Simply try to build the kdelibs3 (or kdegraphic3, or kdenetwork3) port. It will die soon enough with a C++ error. It look like, indeed, a stricter C++ compliance issue, but it is not, because: . it is triggered by something in /usr/include/c++/3.3 itself . it goes away if you remove the ``-pedantic'' from the Makefiles (find work/kdelibs* -name Makefile | \ xargs sed -i "" -e 's,-pedantic,,') Note, that it is, indeed, just -pedantic, not the -pedantic-errors. So much so, I was suggesting to our KDE team to add the post-patch entry to the bsd.kde.mk, that would remove ``-pedantic'' automaticly. Yours, -mi