Date: Tue, 30 Oct 2018 14:13:10 -0500 From: Jason Bacon <bacon4000@gmail.com> To: Mark Linimon <linimon@lonesome.com>, Jan Beich <jbeich@FreeBSD.org> Cc: Mark Linimon <linimon@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r483245 - head/biology/stacks Message-ID: <9ca1854a-e1ec-e5be-b389-58ce52df7b9e@gmail.com> In-Reply-To: <20181030184712.GC9229@lonesome.com> References: <201810280858.w9S8w0sk015320@repo.freebsd.org> <5zxm-1d6y-wny@FreeBSD.org> <20181030184712.GC9229@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/30/18 1:47 PM, Mark Linimon wrote: > On Sun, Oct 28, 2018 at 01:13:41PM +0100, Jan Beich wrote: >> Mark Linimon <linimon@FreeBSD.org> writes: >> Why not USES=compiler:gcc-c++11-lib ? > I didn't realize they were equivalent. > > mcl > It achieves the same effect here, but I'm not crazy about replacing the explicit openmp requirement with a gcc requirement. It's vague and seems like a step backward. If it's not clearly documented that a port requires openmp, someone could inadvertently make a change that disables openmp in the future. It would be nice if we could do something like USES= compiler:openmp,c++11-lib gmake python shebangfix but multiple compiler arguments don't seem to be supported. Or maybe we could add an openmp-c++11-lib argument? -- Earth is a beta site.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ca1854a-e1ec-e5be-b389-58ce52df7b9e>