Thanks Keith. We checked, and indeed libopenblas is not linked against
libomp nor libgomp. We suspect this is because we used conda to install
R and OpenBLAS. So I guess we should be barking up the conda tree instead?
By the way, I also noticed on my home machine (Ubuntu),
/usr/lib/libopenblas
> In order to document the generated Know-How of Optional BLAS Libraries
> Implementation and Tests (For example: OpenBLAS), I have created a
> Mediawiki based wiki page in which anyone can document and discuss any
> issues he/she encounters:
>
> https://kbrproject.miraheze.org/wiki/Main_Page/BLAS
In order to document the generated Know-How of Optional BLAS Libraries
Implementation and Tests (For example: OpenBLAS), I have created a
Mediawiki based wiki page in which anyone can document and discuss any
issues he/she encounters:
https://kbrproject.miraheze.org/wiki/Main_Page/BLAS
I will mys
On 10/01/2018 1:26 PM, Neal Richardson wrote:
Hi,
Since yesterday I'm seeing `R CMD check --as-cran` failures on the
R-devel daily build (specifically, R Under development (unstable)
(2018-01-09 r74100)) for multiple packages:
* checking serialized R objects in the sources ... WARNING
Found file
Hi,
Since yesterday I'm seeing `R CMD check --as-cran` failures on the
R-devel daily build (specifically, R Under development (unstable)
(2018-01-09 r74100)) for multiple packages:
* checking serialized R objects in the sources ... WARNING
Found file(s) with version 3 serialization:
‘build/vignett
I won’t play nicely with a package that combines omp pragmas with calls to BLAS
routines, e.g. something you might get with source Armadillo/Eigen/Blaze code,
for reasons that Benjamin mentioned in his initial email (pthreads vs omp).
Keith
> On Jan 10, 2018, at 1:28 AM, Avraham Adler wrote:
>
