From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Fzj8X-0007lA-S2 for garchives@archives.gentoo.org; Sun, 09 Jul 2006 23:56:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k69Nt3BX018947; Sun, 9 Jul 2006 23:55:03 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k69NoohY005114 for ; Sun, 9 Jul 2006 23:50:51 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 05666642AA for ; Sun, 9 Jul 2006 23:50:50 +0000 (UTC) Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04303-07 for ; Sun, 9 Jul 2006 23:50:42 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 13A0A642E4 for ; Sun, 9 Jul 2006 23:50:41 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Fzj2s-00088e-Oj for gentoo-dev@gentoo.org; Mon, 10 Jul 2006 01:50:38 +0200 Received: from static24-72-114-127.yorkton.accesscomm.ca ([24.72.114.127]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Jul 2006 01:50:38 +0200 Received: from dirtyepic.sk by static24-72-114-127.yorkton.accesscomm.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Jul 2006 01:50:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Ryan Hill Subject: [gentoo-dev] Re: Dying on some CFLAGS instead of filtering them. Date: Sun, 09 Jul 2006 17:51:24 -0600 Message-ID: References: <7c612fc60607091424s467c27e4n665fc3dd4ee2116a@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig07BE0C4AE8E4028C5FDF419F" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: static24-72-114-127.yorkton.accesscomm.ca User-Agent: Thunderbird 1.5.0.4 (X11/20060603) In-Reply-To: <7c612fc60607091424s467c27e4n665fc3dd4ee2116a@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=9232ECA5 Sender: news X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Status: No, score=-2.504 required=5.5 tests=[AWL=0.095, BAYES_00=-2.599] X-Spam-Score: -2.504 X-Spam-Level: X-Archives-Salt: 688383ca-5a5f-415b-8c21-148011f73201 X-Archives-Hash: 2e983f322797f194bb52976eb6881a94 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig07BE0C4AE8E4028C5FDF419F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Denis Dupeyron wrote: > In bug #139412, I ask Paul de Vriese why he thinks python should die > on --fast-math instead of just filtering it. Here's his answer : >=20 > "Denis, quite simple. -ffast-math is broken and short-sighted for a > global flag. > Filtering gives the shortsighted message that it works globally, while > it is > not suited for any package not specifically tested for it. As it breaks= > python, > dieing makes people understand that it does not work on python. It is > better > than the alternative of not looking for it at all." Ebuilds shouldn't die on anything according to the non-interactive portag= e philosophy. I don't know how official that philosophy is though. > This, for me, triggers 3 questions that are gentoo-dev@ material : >=20 > 1) Should all ebuilds that currently filter --fast-math die on its > presence instead of filtering it ? No, that would be a major pain in the ass for anyone wanting to use -fast= -math, which does have legitimate uses. > 2) If yes, are there any other flags that ebuilds should die on ? There's a million, and they're constantly changing. For example, -frename-registers is generally safe on GCC 3.4, broken in 4.0, and enabl= ed by default on 4.1. > 3) Suppose that -ftracer, for example, is one of those, and knowing > that enabling -fprofile-use enables -ftracer, shouldn't ebuilds also > die on use of -fprofile-use ? It's only an example, this situation > will exist for other pairs of flags. >=20 > The hidden question behind these three is : shouldn't we have a > "something" that enables us to safely handle this kind of situations ? > Like some kind of system- and/or architecture-wide flag mask that > could be overriden by the ebuild and/or the user (at his own risk) ? > This could potentialy reduce the number of bugs that poor old bugzie > has to cope with, and simplify ebuild writing and maintenance. Users playing with CFLAGS get to keep the pieces. Trying to dummy-proof = the system doesn't help anyone but the dummies. ;) --de. --------------enig07BE0C4AE8E4028C5FDF419F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQFEsZaCyrvh8ZIy7KURAm9RAKDiuM5hmY7tYHmj5DFQvv/aC+ZNaACffqeT 7b1B77V9MI740NJXd+GTayM= =NlDp -----END PGP SIGNATURE----- --------------enig07BE0C4AE8E4028C5FDF419F-- -- gentoo-dev@gentoo.org mailing list