similar to: Fixed BLAS tests for external BLAS library

>>>>> Tomas Kalibera <tomas.kalibera at gmail.com> >>>>> on Fri, 5 Jan 2018 00:41:47 +0100 writes: > In practical terms, failing tests are not preventing anyone from using > an optimized BLAS/LAPACK implementation they trust. Building R with > dynamically linked BLAS on Unix is supported, documented and easy for > anyone who

In practical terms, failing tests are not preventing anyone from using an optimized BLAS/LAPACK implementation they trust. Building R with dynamically linked BLAS on Unix is supported, documented and easy for anyone who builds R from source. It is also how Debian/Ubuntu R packages are built by default, so R uses whichever BLAS is installed in the system and the user does not have to build

Greetings - For a host of reasons I chose (was forced) to upgrade my multi-Opteron box from Fedora 7 -> Fedora 8. In the process, I also updated the ACML I had installed from 4.0.0 to 4.1.0. While I get no errors (that I can find) in the config -> make -> make install sequence, I'm pretty sure (based on some benchmarks) that I'm not getting BLAS and/or Lapack to compile in. So,

Greetings - A quick perusal of some of the posts to this maillist suggest the level of the questions is probably beyond someone working at my level, but at the risk of looking foolish publicly (something I find I get increasingly comfortable with as I get older), here goes: My research group recently purchased a multi-Opteron system (bunch of 880 chips), running 64-bit RHEL 4 (which we have

Well, CentOS 5.3, which amounts to the same thing. I recently decided to upgrade my main research machine from Fedora Core 8 -> CentOS 5.3. Basically, I was looking to move to a distro with longer 'term-of-life' than the release schedule for Fedora currently allows. The machine is a multi-Opteron box, so both 32- and 64-bit apps natively supported. Since I do a lot of 'linear

Hello. I am a Linux neophyte and know almost nothing ?about compiling, so I would appreciate any help and advice y'all would care to offer. I am trying to compile the 64 bit version of R using a tuned ATLAS and LAPACK (ATLAS 3.9.24). I am running Ubunto 10.04 LTS (through wubi, FWIW). The ATLAS and LAPACK files (atlas.so, f77blas.so, lapack.so, and cblas.so) are sitting in the folder

Greetings - I'm trying to compile R under GNU/Linux (RHEL 4) on a multi-Opteron box, with ACML support. First, I downloaded and installed ACML 3.5 - GNU version, although I'm not entirely sure what the differences are - from the AMD website. The ACML libraries were installed to /opt/acml3.5.0/ Second, I ran ./configure --with-blas='-lacml' The configure went fine,

I'm trying to build R-devel with AMD's ACML. I downloaded version 3.0.0 64bit for gfortran (acml-3-0-0-gfortran-64bit.tgz) and copied the libraries to /usr/local/lib. When I configure R to build against the ACML library, how do I know if the library has been detected and will be used? I run 'configure' with the '--with-blas=-lacml' flag and am using gcc 4.0.2 (with

On Mon, May 6, 2019 at 11:55 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 5/4/19 6:49 PM, Steve Kargl wrote: > > On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas K?nig wrote: > >>> - figure out Fortran2003 specification for C/Fortran interoperability > >>> -- this _sounds_ like the right solution, but I don't think many >

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 Tomas, Thanks for your answer. Indeed, I checked and my R-3.4.1 installed from the ubuntu repository use 'libopenblasp-r0.2.18.so' while my R-3.3.2 that I did compiled on my machine use 'libRblas.so' which explain the difference of behavior. I will use RhpcBLASctl to avoid issue when combining matrix product and other multi-threading package. Maybe this point regarding

Have been running 2.5.1 on my multi-pro Opteron box running Fedora Core 5 with no problems. Had compiled previously with no problems. However, for a variety of reasons (mostly due to ACML upgrade), I tried a recompile using the following sequence of commands (note I'm compiling in ACML support for blas): LD_LIBRARY_PATH=/opt/acml3.6.1/gfortran64/lib export LD_LIBRARY_PATH ./configure

I am encountering segfaults when checking the lme4 package on an Athlon64 system if I use the acml blas. R was built as a 64-bit application using the GCC 4.0.3 compiler suite including gfortran. The version of acml is 3.5.0 gfortran64. I do not encounter the segfaults when I compile R with R's built-in BLAS. The errors occur in the first example in lme4 in a call to lmer. It looks like

Dear R Core Team, I wish to report what can be viewed as a bug or at least a strange behavior in R-3.4.1. I ask my question here (as recommended on https://www.r-project.org/bugs.html) since I am not member of the R's Bugzilla. When running 'R --vanilla' from the command line, the standard matrix product is by default based on BLAS and multi-threaded on all cores available on

On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas K?nig wrote: > > > - figure out Fortran2003 specification for C/Fortran interoperability > > -- this _sounds_ like the right solution, but I don't think many > > understand how to use it and what is implied (in particular, will > > it require making changes to LAPACK itself?) > > That would actually be fairly

I get an R error and no segfault: > parse(textConnection(text), srcfile = srcfile) Error in parse(textConnection(text), srcfile = srcfile) : test.r:1:1: unexpected $end 1: ? ^ This is R 4.3.0, so maybe the bug has been introduced since then... Version and system info: > version _ platform x86_64-pc-linux-gnu arch x86_64 os linux-gnu system

I am trying to get R to use the ACML BLAS, specifically the 'mp' version for multithreading. I have installed acml-4-4-0-gfortran-64bit I added /opt/acml4.4.0/gfortran64_mp/lib to $LD_LIBRARY_PATH. I ran: sudo ./configure --with-blas="-L/opt/acml4.4.0/gfortran64_mp/lib -lacml_mp" At the end of the configuration, the only external library listed is readline, and at the end

I have problems building R 2.11.1 with an external BLAS. I've tried several with several libraries: # ACML: export LD_LIBRARY_PATH=/site/VERSIONS/acml-3.6.0/gfortran64_int64/lib BLAS=--with-blas="-L/site/VERSIONS/acml-3.6.0/gfortran64_int64/lib -lacml" LAPACK=--with-lapack # MKL 11: BLAS=--with-blas="-L/site/VERSIONS/intel-11.1/mkl/lib/em64t -lmkl_gf_lp64 -lmkl_sequential

Dear R-devel team, I've encountered problems with recent Rs (>= 3.5.3) and MKL. I've followed Dirk's (http://dirk.eddelbuettel.com/blog/2018/04/15/) and Intel's ( https://software.intel.com/en-us/articles/quick-linking-intel-mkl-blas-lapack-to-r) instructions and many versions of MKL. All works fine in my Ubuntu 18 setup for R 3.5.2 and older. Carrying out the install and

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