[Bug 247753] Mk/Uses/compiler.mk: compiler:openmp still forces the use of gcc
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jul 4 04:43:08 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247753
Bug ID: 247753
Summary: Mk/Uses/compiler.mk: compiler:openmp still forces the
use of gcc
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: tjlegg at gmail.com
CC: jhale at FreeBSD.org, kwm at FreeBSD.org
CC: jhale at FreeBSD.org, kwm at FreeBSD.org
I'd like to thank the FreeBSD team for enabling openmp for the base clang.
Unfortunately, most of the ports that have an OPENMP option, just default to
OPENMP_USES= compiler:openmp.
If you look at Mk/Uses/compiler.mk, the openmp option forces the use of gcc,
which defeats the purpose of having base being openmp-enabled.
I've altered a few ports like graphics/libraw, graphics/ImageMagick7, and
math/fftw3 to have the OPENMP option to provide OPENMP_FLAGS= -lm -lomp and
LDFLAGS+= ${OPENMP_FLAGS} instead of OPENMP_USES= compiler:openmp.
These libraries compile successfully without a gcc9 dependency. Digikam tells
that its raw demosaicing is now parallelised based on libraw having a
functional openmp.
Rather than hand edit port Makefiles, would it be possible to update the
compiler:openmp option to reflect the work that has landed in base?
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list