On 06/06/2019 16:39, Simon Urbanek wrote:
Jon,
some time ago Apple's clang has silently dropped -fopenmp so we were able to at
least keep it in the flags even if it wasn't actually using it. Still, it was
only dropping it, it wasn't actually generating any parallel code, so there was
real
Jon,
some time ago Apple's clang has silently dropped -fopenmp so we were able to at
least keep it in the flags even if it wasn't actually using it. Still, it was
only dropping it, it wasn't actually generating any parallel code, so there was
real point in using it. That's when we decided to
Hi James,
> > Lack of OpenMP support in Apple’s build of Clang is cited as one reason for
> > not using it in CRAN builds
>
> From R 3.4.x forward, OpenMP has been enabled in CRAN builds as the toolchain
> is using a custom compiler.
I’m aware of that, but this makes building packages from
Greetings and Salutations Jon,
> Lack of OpenMP support in Apple’s build of Clang is cited as one reason for
> not using it in CRAN builds
From R 3.4.x forward, OpenMP has been enabled in CRAN builds as the toolchain
is using a custom compiler.
You can see this with regard to the work done to
Dear all,
Lack of OpenMP support in Apple’s build of Clang is cited as one
reason for not using it in CRAN builds, but this is only partly true:
after installing libomp from Homebrew, I have been adding
“-Wp,-fopenmp” to CXXFLAGS and CFLAGS (and “-lomp” to LIBS) to my
builds for a while, and
