From owner-freebsd-ports@FreeBSD.ORG Tue Sep 7 19:58:50 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26AF116A4CE for ; Tue, 7 Sep 2004 19:58:50 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B670343D48 for ; Tue, 7 Sep 2004 19:58:44 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.12.11/8.12.11) with ESMTP id i87JwY8C084492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Sep 2004 12:58:35 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.11/8.12.11/Submit) id i87JwSNh002559; Tue, 7 Sep 2004 12:58:28 -0700 (PDT) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 07 Sep 2004 12:58:28 -0700 (PDT) From: John Polstra To: Charles Swiger X-Bogosity: No, tests=bogofilter, spamicity=0.492039, version=0.14.5 cc: FreeBSD Ports Subject: Re: Best way to override user's CFLAGS in a port? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 19:58:50 -0000 On 07-Sep-2004 Charles Swiger wrote: > Users would prefer the software to build properly, so yes, doing > something to switch -Ox to plain -O is better than marking the port > BROKEN. > > I don't think that changing a specific flag in a port which needs to do > so is unreasonable, but I dislike the notion of second-guessing the > end-user. The whole point of preserving CFLAGS set in /etc/make.conf > or via the environment is to make it easy for people to build all of > the software using whatever flags they want. Agreed, but some user preferences (for example, "-g") are more important than others (such as optimization levels). > Can we help you fix the issues with ezm3 when compiled with -O2, rather > than figuring ways to hack CFLAGS...? In the long run, probably yes. At the moment I'm just trying to staunch the flow of bug reports for this thing. John