A
I had a .Renviron file which was the culprit.
> On 25.04.2020, at 17:40, Kevin Ushey wrote:
>
> R --vanilla -s -e "writeLines(.libPaths())"
[[alternative HTML version deleted]]
___
R-SIG-Mac mailing list
R-SIG-Mac@r-project.org
https
The following works for me on macOS 10.15.4 using Apple Clang + libomp
from LLVM 10 (via Homebrew).
Install libomp from Homebrew with:
brew install libomp
Then, put the following in ~/.R/Makevars
CPPFLAGS += -I/usr/local/opt/libomp/include -Xclang -fopenmp
LDFLAGS += -L/usr/local/op
Can you confirm that you see this even with:
R --vanilla -s -e "writeLines(.libPaths())"
If you don't see the issue there, the most likely culprit is something
in a .Rprofile that's causing the old library path to be used.
Kevin
On Sat, Apr 25, 2020 at 4:59 AM Bob Rudis wrote:
>
> Can you
I second this request. Dropping OpenMP support in R v4.0 on Mac is
unfortunate. My R package is highly parallelized via OpenMP, and many of my
end-users take advantage of the excellent speedups. It would be much
appreciated if user-level instructions could be provided for how to enable
OpenM
Can you try it with the "tar" method and see if it has the same behavior?
I use the gzip'd tar files and have multiple versions running on
multiple Macs and .libPaths() is not exhibiting that behavior.
On Sat, Apr 25, 2020 at 5:47 AM Erich Subscriptions
wrote:
>
> I installed R 4.0 on 2 machines
I installed R 4.0 on 2 machines, an iMac and a Macbook Pro.
Before that, I installed RSwitch and did what the site tells to do:
sudo pkgutil --forget org.r-project.R.el-capitan.fw.pkg \
--forget org.r-project.x86_64.tcltk.x11 \
--forget org.r-project.x86_64.texinfo \
