From owner-svn-ports-all@freebsd.org Mon Nov 9 12:01:08 2015 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E08E5A2AEE4; Mon, 9 Nov 2015 12:01:08 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE6BC189B; Mon, 9 Nov 2015 12:01:08 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from [192.168.0.129] (vie-188-118-249-117.dsl.sil.at [188.118.249.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 0E5F53F447; Mon, 9 Nov 2015 07:01:05 -0500 (EST) Date: Mon, 9 Nov 2015 13:01:04 +0100 (CET) From: Gerald Pfeifer To: Adam Weinberger , Alexey Dokuchaev , Guido Falsi cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r388648 - in head/net: asterisk11 asterisk13 In-Reply-To: <564044BC.5050203@FreeBSD.org> Message-ID: References: <201506052330.t55NUBZL020965@svn.freebsd.org> <564044BC.5050203@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 12:01:09 -0000 On Sun, 8 Nov 2015, Adam Weinberger wrote: > What are some of the other common intentions of a GCC option? Here is the full list I found: cad/ghdl/Makefile:GCC_DESC= Code generator is GCC (mature) lang/erlang-runtime15/Makefile:GCC_DESC= Use current GCC lang/erlang-runtime16/Makefile:GCC_DESC= Use current GCC lang/erlang-runtime17/Makefile:GCC_DESC= Use current GCC lang/erlang-runtime18/Makefile:GCC_DESC= Use current GCC lang/erlang/Makefile:GCC_DESC= Use current GCC lang/gambit-c/Makefile:GCC_DESC= Build with GCC lang/ghc/Makefile:GCC_DESC= Build with GCC (from ports) lang/ghc/bsd.cabal.options.mk:GCC_DESC= Build with GCC (from ports) multimedia/x264/Makefile:GCC_DESC= Use current GCC net/asterisk11/Makefile:GCC_DESC= Use GCC from ports net/asterisk13/Makefile:GCC_DESC= Use GCC from ports security/cryptopp/Makefile:GCC_DESC= Build with current GCC www/mod_spdy/Makefile:GCC_DESC= Build with current GCC On Mon, 9 Nov 2015, Alexey Dokuchaev wrote: > OTOH, those cases should be a minority, so having sensible defaul GCC_DESC > makes sense after all. Shall it be "Use GCC from ports" or "Build with > current GCC"? Looking at the above I'd vouch for "Build with current GCC" which should work for all but cad/ghdl. Which can easily keep it's current wording (and thus override the default). On Mon, 9 Nov 2015, Guido Falsi wrote: > IMHO usually the GCC option should be meant to be used when one wants > GCC from ports, while using a base compiler should should be a default > or the alternative. Sooo, any objections towards adding the following Index: Mk/bsd.options.desc.mk =================================================================== --- Mk/bsd.options.desc.mk (revision 401088) +++ Mk/bsd.options.desc.mk (working copy) @@ -102,6 +102,7 @@ FTP_DESC?= FTP protocol support FTPS_DESC?= FTP with SSL/TLS support FUSE_DESC?= FUSE (Filesystem in Userspace) support +GCC?= Build with current GCC GCONF_DESC?= GConf configuration backend support GCRYPT_DESC?= Use GNU crypt library instead of OpenSSL GD_DESC?= GD graphics library support and removing GCC_DESC= from all Makefiles except for cad/ghdl/Makefile? Gerald