search for: openmp64

...y above. I should have said: I *can't* > answer the question re USE_LOCKING=1. :) > Those other suggestions are really helpful too; I really didn't > understand what the difference was (I'm still not clear what the > differences are between say openblas-openmp and openblas-openmp64), > but I did get R to pass mgcv's thread safe test with both > openblas-openmp and blis-openmp, so I have aliased those options for > use too. Basically, openblas has a number of features that can be enabled or disabled: 64-bit integer support, threading and parallelization of certai...

On Wed, 27 May 2020 at 21:40, Gavin Simpson <ucfagls at gmail.com> wrote: > > Thanks I?aki, that is exactly what i was looking for, esp the last > option which I have now configured as an alias for easy remembering. > > I can answer the question re USE_LOCKING=1. I think that using both > those options is required to get thread-safety even if openblas was > compiled for

...re was a typo in my reply above. I should have said: I *can't* answer the question re USE_LOCKING=1. Those other suggestions are really helpful too; I really didn't understand what the difference was (I'm still not clear what the differences are between say openblas-openmp and openblas-openmp64), but I did get R to pass mgcv's thread safe test with both openblas-openmp and blis-openmp, so I have aliased those options for use too. Just using blis ( /lib64/blisblas/libblas.so.3 ) was generating a segfault when running the mgcv test. Really appreciate the help! All the best G On Wed...

...aded openblas built locally. I have installed $ yum list installed | grep openblas openblas.x86_64 0.2.11-1.fc20 @updates openblas-devel.x86_64 0.2.11-1.fc20 @updates openblas-openmp.x86_64 0.2.11-1.fc20 @updates openblas-openmp64.x86_64 0.2.11-1.fc20 @updates openblas-serial64.x86_64 0.2.11-1.fc20 @updates openblas-threads.x86_64 0.2.11-1.fc20 @updates openblas-threads64.x86_64 0.2.11-1.fc20 @updates The locally built openblas returned the following informa...