Date: Mon, 9 Nov 2015 08:28:58 -0700 From: Adam Weinberger <adamw@adamw.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: Alexey Dokuchaev <danfe@FreeBSD.org>, Guido Falsi <madpilot@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r388648 - in head/net: asterisk11 asterisk13 Message-ID: <077EDBDC-8EF1-44FA-9D17-90345C2956F5@adamw.org> In-Reply-To: <alpine.LSU.2.20.1511091255000.2548@anthias> References: <201506052330.t55NUBZL020965@svn.freebsd.org> <alpine.LSU.2.20.1511082001320.2548@anthias> <564044BC.5050203@FreeBSD.org> <alpine.LSU.2.20.1511091255000.2548@anthias>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 9 Nov, 2015, at 5:01, Gerald Pfeifer <gerald@pfeifer.com> wrote: >=20 > On Sun, 8 Nov 2015, Adam Weinberger wrote: >> What are some of the other common intentions of a GCC option? >=20 > Here is the full list I found: >=20 > cad/ghdl/Makefile:GCC_DESC=3D Code generator is GCC (mature) > lang/erlang-runtime15/Makefile:GCC_DESC=3D Use current GCC > lang/erlang-runtime16/Makefile:GCC_DESC=3D Use current GCC > lang/erlang-runtime17/Makefile:GCC_DESC=3D Use current GCC > lang/erlang-runtime18/Makefile:GCC_DESC=3D Use current GCC > lang/erlang/Makefile:GCC_DESC=3D Use current GCC > lang/gambit-c/Makefile:GCC_DESC=3D Build with GCC > lang/ghc/Makefile:GCC_DESC=3D Build with GCC (from ports) > lang/ghc/bsd.cabal.options.mk:GCC_DESC=3D Build with GCC = (from=20 > ports) > multimedia/x264/Makefile:GCC_DESC=3D Use current GCC > net/asterisk11/Makefile:GCC_DESC=3D Use GCC from ports > net/asterisk13/Makefile:GCC_DESC=3D Use GCC from ports > security/cryptopp/Makefile:GCC_DESC=3D Build with = current GCC > www/mod_spdy/Makefile:GCC_DESC=3D Build with current GCC >=20 > 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"? >=20 > 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). >=20 > 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. >=20 > Sooo, any objections towards adding the following >=20 > Index: Mk/bsd.options.desc.mk > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- Mk/bsd.options.desc.mk (revision 401088) > +++ Mk/bsd.options.desc.mk (working copy) > @@ -102,6 +102,7 @@ > FTP_DESC?=3D FTP protocol support > FTPS_DESC?=3D FTP with SSL/TLS support > FUSE_DESC?=3D FUSE (Filesystem in Userspace) support > +GCC?=3D Build with current GCC > GCONF_DESC?=3D GConf configuration backend support > GCRYPT_DESC?=3D Use GNU crypt library instead of OpenSSL > GD_DESC?=3D GD graphics library support >=20 > and removing GCC_DESC=3D from all Makefiles except for = cad/ghdl/Makefile? >=20 > Gerald >=20 What about "Build with current GCC (from ports)"? With or without those parentheses. Then people know that they're about to build/install a new compiler, = which is a large and time-consuming dependency. # Adam --=20 Adam Weinberger adamw@adamw.org http://www.adamw.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?077EDBDC-8EF1-44FA-9D17-90345C2956F5>