similar to: ropenblas package

Dear all, Given that the Intel MKL multithreaded BLAS is now free (https://software.intel.com/en-us/mkl/choose-download, released under the very permissive Intel Simplified Software License, https://software.intel.com/en-us/license/intel-simplified-software-license) and that this BLAS comes out as the fastest in most benchmarks, and that Microsoft R Open compiled against Intel MKL seems to be

Hello, Over time, the FreeBSD R port/package [1] has accumulated some cruft. We've begun an overhaul and the process has generally been positive since most of the local patches and workarounds are no longer necessary. However, we still require a few workarounds. 1. Libjpeg The autotools check for libjpeg >=6b fails even when libjpeg is present (e.g. /usr/local/lib/libjpeg.so.8 exists).

Hi, I can not install packages from source which links to RcppArmadillo on Ubuntu 20.04 (after upgrading from 18.04). The following problem occurs: ** testing if installed package can be loaded from temporary location Error: package or namespace load failed for 'myPackage' in dyn.load(file, DLLpath = DLLpath, ...): unable to load shared object

I've not worked changing underlying computational infrastructure, but developers who do might want to use ideas from FlexiBLAS. Apologies in advance if this is well-known. Best JN > From: Martin Koehler koehlerm at mpi-magdeburg.mpg.de > Date: January 07, 2016 > Subject: FlexiBLAS Version 1.3.0 Release > > It is our pleasure to announce the new release of FlexiBLAS. We do not

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 single thread use. I don't know to what extent Simon has engaged with upstream on this etc. All I know is

Hi Gavin, On Wed, 27 May 2020 at 01:15, Gavin Simpson <ucfagls at gmail.com> wrote: > > Dear list, > > What is the recommended incantation on Fedora 32 to swap out the > openblas BLAS that the packaged (rpm) version of R-core installs for > ATLAS? I'm afraid there is no official mechanism in place to do that yet. There was a proposal [1], but it was never pushed

(CCing the R-devel list, maybe someone will have a better answer.) To be honest, I don't know how to. I wasn't able to configure R to use OpenBLAS using the configure script and options on my Linux Fedora system. I configure it without external BLAS, then replace the libRblas.dylib (.so in my case) with a link to the OpenBLAS dynamic link library. Peter On Tue, May 7, 2019 at 7:39 PM

Thank you, Brad (and others), >>>>> Brad Bell on Mon, 4 Feb 2019 07:21:18 -0700 writes: > I get the failure message. To be specific: adcomp.git> R CMD BATCH --quiet test_nlminb.R adcomp.git> cat test_nlminb.Rout >> f <- function(x) sum( log(diff(x)^2+.01) + (x[1]-1)^2 ) >> opt <- nlminb(rep(0, 10), f, lower=-1, upper=3) >>

Executive summary: I believe revision 86265 makes it more difficult to build R with OpenBLAS on Windows as now the entire LAPACK needs to be built to obtain zspmv. Is there anything that can be done to allow the former behavior to be used, something in Mkrules.local perhaps? Detailed Explanation: I have been building R with OpenBLAS for Windows 64 for over a decade by patching

Of course, even a simpler trick is to launch R as follows: LD_PRELOAD=/lib64/atlas/libsatlas.so.3 R and then the symbols in libsatlas take precedence over libopenblas. Or a mix between both alternatives, i.e., setting LD_PRELOAD=/path/to/some/link R and then change that link to point to openblas, atlas... Whatever suits you best. I?aki On Wed, 27 May 2020 at 11:00, I?aki Ucar <iucar at

Dear list, What is the recommended incantation on Fedora 32 to swap out the openblas BLAS that the packaged (rpm) version of R-core installs for ATLAS? I'm running into some problems with some big models I want to fit using the mgcv package, and openblas is apparently not thread safe and is causing problems. I have the following installed: $ dnf list installed | grep ^R R-core.x86_64

Dear List, I am trying to build R on Fedora against a threaded openblas installed from Fedora's yum repos, or alternatively swap out libRblas.so with a threaded 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

Dear All, I am building R from source[1], following what is done in "rules" for building Debian's R. But the R I generate, in contrast to the standard Debian's R, will not change the BLAS and LAPACK libraries it uses when I change them via "update-alternatives". I have no idea what I am doing wrong (but, somehow, I've been quite capable of making the same

On 2020-07-15 14:36, Dirk Eddelbuettel wrote: > > G?ran, > > This is not an easy email to reply to because it _contains nothing > reproducible_. Thanks Dirk, Sorry about that, but my real question was (see below): "Is the problem that openblas uses C versions of blas?" That is, do I need to change F77_CALL(name)(...); to cblas_name(...); everywhere? And if so, is

It seems that reproducibility across systems is also an issue with multithreaded BLASes: https://hal.archives-ouvertes.fr/hal-01202396/file/exblas.pdf On Sun, Dec 17, 2017 at 11:50 AM, Keith O'Hara <keith.ohara at nyu.edu> wrote: > On point 1): > > The standard approach seems to favor the reference BLAS for reasons other > than speed. > > For example, vecLib,

Hello, I thought that I should try openblas when building a CRAN package containing lots of old (twentieth century) C-code with frequent calls to blas and lapack routines. I have the following options on my Ubuntu 20.04 machine: Selection Path Priority Status ------------------------------------------------------------ * 0

G?ran, This is not an easy email to reply to because it _contains nothing reproducible_. On 15 July 2020 at 13:24, G?ran Brostr?m wrote: | Hello, | | I thought that I should try openblas when building a CRAN package | containing lots of old (twentieth century) C-code with frequent calls to | blas and lapack routines. I have the following options on my Ubuntu | 20.04 machine: | |

On point 1): The standard approach seems to favor the reference BLAS for reasons other than speed. For example, vecLib, Apple's multi-threaded BLAS library, is not the default choice for macOS binaries due to concerns about 'precision'. See: https://cloud.r-project.org/bin/macosx/RMacOSX-FAQ.html#Whic h-BLAS-is-used-and-how-can-it-be-changed_003f This doesn't appear to be Mac-

Il 30/04/20 03:39, Dirk Eddelbuettel ha scritto: > > On 30 April 2020 at 03:26, Samuele Carcagno wrote: > | I'm not familiar with the internals of `viridisLite`, so I'm not sure > | I'd be able to help there. I could open a bug report on the > | `viridisLite` repo and see if the author has suggestions on how to > | narrow down the issue. > > It would help if

Do those issues still arise when OpenBLAS is compiled with USE_OPENMP=1 ? Keith > On Jan 9, 2018, at 6:03 PM, Benjamin Tyner <btyner at gmail.com> wrote: > > Please pardon my ignorance, but doesn't OpenBLAS still not always play nicely with multi-threaded OpenMP? (for example, don't race conditions sometimes crop up)? If so, it might be nice to have the ability to