From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21776 invoked by alias); 14 Jan 2008 10:34:34 -0000 Received: (qmail 21765 invoked by uid 22791); 14 Jan 2008 10:34:33 -0000 X-Spam-Check-By: sourceware.org Received: from fg-out-1718.google.com (HELO fg-out-1718.google.com) (72.14.220.153) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jan 2008 10:34:05 +0000 Received: by fg-out-1718.google.com with SMTP id d23so2073281fga.28 for ; Mon, 14 Jan 2008 02:34:02 -0800 (PST) Received: by 10.86.99.9 with SMTP id w9mr6085038fgb.44.1200306842523; Mon, 14 Jan 2008 02:34:02 -0800 (PST) Received: from scientist-2.mobile.usilu.net ( [195.176.176.226]) by mx.google.com with ESMTPS id 4sm4961369fge.8.2008.01.14.02.34.01 (version=SSLv3 cipher=RC4-MD5); Mon, 14 Jan 2008 02:34:01 -0800 (PST) Message-ID: <478B3A9B.7000104@gnu.org> Date: Mon, 14 Jan 2008 11:03:00 -0000 From: Paolo Bonzini User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: =?UTF-8?B?SXNtYWlsIETDtm5tZXo=?= CC: Andreas Schwab , Gabriel Dos Reis , gcc@gcc.gnu.org, =?UTF-8?B?TWFudWVsIEzDs3Blei1JYsOhw7Fleg==?= Subject: Re: Changes in C++ FE regarding pedwarns to be errors are harmful References: <200801082328.22849.ismail@pardus.org.tr> <200801131734.42932.ismail@pardus.org.tr> <200801131810.30493.ismail@pardus.org.tr> In-Reply-To: <200801131810.30493.ismail@pardus.org.tr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2008-01/txt/msg00200.txt.bz2 Ismail Dönmez wrote: > Sunday 13 January 2008 18:03:20 tarihinde Andreas Schwab şunları yazmıştı: >> Ismail Dönmez writes: >>> That was just an example, real life testcase shows that problem stems >>> from autoconf and its config.h. Projects end up defining things like >>> HAVE_STDLIB_H twice which is not harmful at all but now causes an error >>> if g++ is used. >> Redefinitions with the same replacement list are not an error. > > Ok but that still doesn't cover the general use of > > #define PACKAGE_NAME foobar We had to fix it ourselves for libffi as part of switching to autoconf 2.50+. The point is that installing config.h headers is broken by design -- and this is not something that the GCC community states. See for example http://www.cygwin.com/ml/automake/2000-10/msg00116.html "Unfortunately, people are being lulled into a false sense of security, because installing config.h appears to work while it is an uncommon practice. Things will go downhill fast if this becomes common practice -- imagine the chaos that we would have if gtk.h indirectly #included a raw (i.e. with rewriting prior to installation) config.h, which set up a whole bunch of HAVE_foo macros and VERSION's that you don't want to cope with when you use libgtk. Even worse what if the gnome headers installed another conig.h with overlapping and contradicting macros...." which warned about this already 8 years ago. Sweet. Why not fixing the handful of packages with a /^#define PACKAGE/d, instead of adding -fpermissive to the 50 users of those broken packages? Paolo