similar to: About FlexiBLAS in the R-admin docs

On 10/11/23 23:12, George Ostrouchov wrote: > I agree that the "R Installation and Administration" guide statement about FlexiBLAS needs an update. Standard R in CentOS Stream 9, which is now downstream from Fedora, gives the following result for Matrix products in sessionInfo(): > >> sessionInfo() > R version 4.3.1 (2023-06-16) > Platform: x86_64-redhat-linux-gnu

Hi, R has been built against FlexiBLAS in rawhide [1, 2]. These are the R packages that need to be rebuilt: R-ape-0:5.4-2.fc33.x86_64 R-expm-0:0.999.4-7.fc33.x86_64 R-gee-0:4.13.20-4.fc33.x86_64 R-gss-0:2.2.2-3.fc33.x86_64 R-igraph-0:1.2.5-3.fc33.x86_64 R-msm-0:1.6.8-5.fc33.x86_64 R-preprocessCore-0:1.50.0-4.fc33.x86_64 R-qtl-0:1.46.2-4.fc33.x86_64 R-quadprog-0:1.5.8-5.fc33.x86_64 Could

? Tue, 21 May 2024 08:00:11 +0000 Dario Strbenac via R-devel <r-devel at r-project.org> ?????: > Would a less resource-intensive value, such as 1, be a safer default > CPU value for confint? Which confint() method do you have in mind? There is at least four of them by default in R, and many additional classes could make use of stats:::confint.default by implementing vcov(). >

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

Hi Ivan, An apology, I was away for quite a bit. To reproduce the setup: I have been using the default GCC in RHEL 9.1. gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-redhat-linux Configured with: ../configure --enable-bootstrap --enable-host-pie

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

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

Seems like this in 83986 [1] needs a fix in Lapack.c: if (dladdr((void *) F77_NAME(ilaver), &dl_info)) { char buf[PATH_MAX+1]; char *res = realpath(dl_info.dli_fname, buf); if (res) { SEXP nfo = R_NilValue; if (strstr(res, "flexiblas")) nfo = R_flexiblas_info(); if

> On 6 Feb 2019, at 10:58, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > ..... > --------------------------------------------------------------------------- > > I summarize what has been reported till: > > Failure in these cases > ======== > 1. Kasper K ("Scientific Linux", self compiled R, using Intel's MKL > for BLAS/LAPACK)

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

Hello, macosx 10.13.6, Rdevel r76458 I'm trying to compile against openblas to reproduce an error on the CRAN check page (my package is clean under winbuilder and all but one of the checks). I've downloaded and installed openblas 0.3.7 but I am not 100% sure that it is being used by R. Using ./configure --with-blas="-lopenblas" Then running R to discover the PID I get:

I’ve installed R 3.1 with the latest Fedora rpm (R-3.1.0-5.el6.x86_64.rpm) and I run into some issues with openblas. I’ve documented this with an open question on stack overflow here: http://stackoverflow.com/questions/24158372/openblas-r-3-1-and-fedora-centos-dist Basically before 3.1 I had 3.02 and I was able to install and use openblas following the instruction from official CRAN

I run Fedora 22 R package. It is build with --with-lapack \ --with-blas \ --enable-R-shlib \. As the machine will act as a server with lots of R data computing, I try to optimize my R package. At first, I installed parallel_studio_xe_2016 with a free one year licence. Then, I build a package for R with Intel MKL and compiler. This took me lots of time as it was my first .rmp build. I finally

Hi all, I have the issue: icc -std=c99 -std=gnu11 -I../../src/extra -I../../src/extra/xdr -I. -I../../src/include -I../../src/include -I/usr/local/include -I../../src/nmath -DHAVE_CONFIG_H -fopenmp -fpic -g -O3 -wd188 -ip -mp -c eval.c -o eval.o arithmetic.c(66): warning #274: declaration is not visible outside of function int matherr(struct exception *exc) ^

? Wed, 8 May 2024 16:59:25 +0000 Simon Andrews <simon.andrews at babraham.ac.uk> ?????: > The lapack libraries are: > > $ rpm -qa | grep lapack > lapack-3.9.0-10.el9.x86_64 > lapack64_-3.9.0-10.el9.x86_64 > lapack64-3.9.0-10.el9.x86_64 > lapack-devel-3.9.0-10.el9.x86_64 Thanks for this information! I figured out I needed to enable the "PowerTools/CRB" repo,

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

I think the thing that is missing is a simple way for end users on windows to replace blas/lapack libraries with MKL-a package that you install that puts the libraries in the right place. Microsoft provides something for their distro, but we don't have the equivalent if you get R from cran. On 29 October 2017 at 22:01, Kenny Bell wrote: | User here: incorporating Intel's MKL, as MRO

Thank you very much Dirk! Le mer. 13 mai 2020 ? 14:59, Dirk Eddelbuettel <edd at debian.org> a ?crit : > > Salut Adrien, > > It appears to be a bad OpenMP and and OpenBLAS interaction you can (for > now) > avoid) by replacing the 'pthread' variant of OpenBLAS with the OpenMP > version > (see the thread for details). Doing > > sudo apt install

Dear Miguel Esteva, I couldn't get a Red Hat "ubi9" container to install enough dependencies to build R. Is there a way to reproduce your setup on a virtual machine somewhere? On Fri, 3 May 2024 00:42:43 +0000 Miguel Esteva via R-help <r-help at r-project.org> wrote: > *** caught segfault *** > > address 0x1801fa8f70, cause 'memory not mapped' > >

Note that 'intel 2022' is a bit vague. The current version is 2023.1.0, and that has both the 'classic' (icc/icpc/ifort which it seems you used) and new (icx/ixpx/ifx) compilers -- the former are said to be going to be discontinued later this year. R did not know about ifx so did not build with the new set. The parts of the manual Tomas referred to were about the old