specific reason, why we do not (yet) have openmp support for
> > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd
> > > expect compiler:openmp to set
> > >
> > > LIB_DEPENDS+= libomp.so:devel/openmp
> > >
> > > for
On Mon, 7 Nov 2016 18:59:26 -0300
"Nilton Jose Rizzo" wrote:
> Em Mon, 7 Nov 2016 22:12:59 +0100, Matthieu Volat escreveu
> > On Mon, 7 Nov 2016 16:59:36 +
> > Brooks Davis wrote:
> > [...]
>
> I have one question about a llvm and clang ports.
specific reason, why we do not (yet) have openmp support for
> > > clang via compiler:openmp? With devel/openmp in the ports tree, I'd
> > > expect compiler:openmp to set
> > >
> > > LIB_DEPENDS+= libomp.so:devel/openmp
> > >
> > > for
On Mon, 7 Nov 2016 16:59:36 +
Brooks Davis <bro...@freebsd.org> wrote:
> On Sun, Nov 06, 2016 at 08:36:22AM +0100, Marcus von Appen wrote:
> > Hi,
> >
> > is there a specific reason, why we do not (yet) have openmp support for
> > clang via compiler:openm
Hi,
is there a specific reason, why we do not (yet) have openmp support for
clang via compiler:openmp? With devel/openmp in the ports tree, I'd
expect compiler:openmp to set
LIB_DEPENDS+= libomp.so:devel/openmp
for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a
per-port level