similar to: tuned BLAS

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

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

A couple of years ago (in 2008, using R 2.7.x, I believe) I noted that using the configure switch --enable-R-shlib when buildig R made configure ignore any specified external LAPACK library and use the internal one insted. I asked why, and was told it was intentional. Now, with R 2.15.1, I see that it at least appears that this is no longer the case. I've run configure like this:

A couple of years ago I noted that using the configure switch --enable-R-shlib when buildig R made configure ignore any specified external LAPACK library (I cannot recall if also the BLAS specification was ignored) and use the internal one insted. I asked why, and was told it was intentional. Now, with R 2.15.1, I see that it at least appears that this is no longer the case. I've run

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

On Mon, Aug 24, 2015 at 11:29 AM, Bj?rn-Helge Mevik <b.h.mevik at usit.uio.no> wrote: > arnaud gaboury <arnaud.gaboury at gmail.com> writes: > >> - Intel MKL: this is part of Intel Parallel Studio and is a paid >> software. Now, there is the MKL package distributed by >> Revolutionanalytics, but I am not certain how this can be distributed >> for free. Is

I want to build R optimized, with either MKL, OpenBLAS or ATLAS. My OS: Fedora 22 Hardware: CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 Thread(s) per core: 2 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz I am a little confused when it comes to choose a method and would like to hear your experiences. If I am right, I have 3 possibilities: -

I believe that actually means configure was able to use the BLAS you specified (MKL in this case). You can scan through config.log to make sure. Andy > From: > > Fedora Core 3 > > I installed the Intel MLk, > > and tried : --with-blas="-lmkl -lguide -lpthread" > > and got : External libraries: readline, BLAS(generic) > > thus I'm

> I would appreciate any insights over compiling R 3.4 with Intel MKL -- I have been successful until R 3.3.3 but now it stops complaining about pcre though it worked without Intel MKL as follows, I successfully built R-rc_2017-04-19_r72555.tar.gz with icc & MKL on centos 7 with this: # https://software.intel.com/en-us/articles/build-r-301-with-intel-c-compiler-and-intel-mkl-on-linux#

Hi all, I managed to at least compile R-patched (2002-01-08) against MKL 5.1 (not beta). The release notes for MKL said that the libraries are threaded, and the test codes needed to be linked against the pthread library. Therefore I added -lpthread flag in config.site for R-patched, and the compile went through. However, when I did make check, it choked on a call to La.eigen, complaining that

Ryan Novosielski <novosirj at rutgers.edu> writes: > Hi there, > > I initially asked about this on r-help and was told this might be a better venue. I?m not really convinced from reading the posting guide, but I?ll give it a shot. It was also suggested that the R-Project doesn?t really care about building with ?non-standard? compilers, but I can?t find any evidence of that on the

Hi, After building R 2.14.1 on a Linux system (SUSE Linux Enterprise Server 11 (x86_64) ), I ran "make check" but it halted with the foll error: Testing examples for package ?base? Error: testing 'base' failed Execution halted I looked in <build dir>/test/Examples/base-Ex.Rout.fail and found the foll: *******EXCERPT ***** ... > ### ------- Pickyness Flags :

Hi, I'm trying to follow the R-admin instructions for using MKL10 as the external BLAS compiling R-2.6.2 under Linux on a RH EL head node of a cluster. The configure process seems to have problems when it checks for dgemm in the BLAS. I'm using configure as: ./configure CC=icc F77=ifort --with-lapack="$MKL" --with-blas="$MKL" where $MKL is defined as in R-admin

Hello, I compiled R-2.15.2 with linux intel compilers (see below). when I execute some R code on a // 4 proc x 4 cores // server (export MKL_NUM_THREADS = 16) very often I have the situations where only one processor (4 cores) is active instead of 4 (16 cores) ! do you know this fact depends on what ? thank you ! P.S. many functions of R are single-threaded, is there a simple way to make them

On Fri, Sep 4, 2015, 9:24 AM Bj?rn-Helge Mevik <b.h.mevik at usit.uio.no> wrote: arnaud gaboury <arnaud.gaboury at gmail.com> writes: > After a few days of reading and headache, I finally gave a try at > building R from source with Intel MKL and ICC. Documentation and posts > on this topic are rather incomplete, sometime fantasist et do not give > much explanations about

arnaud gaboury <arnaud.gaboury at gmail.com> writes: > After a few days of reading and headache, I finally gave a try at > building R from source with Intel MKL and ICC. Documentation and posts > on this topic are rather incomplete, sometime fantasist et do not give > much explanations about configure options. > As I am not sure if mine is correct, I would appreciate some

On Sat, 2015-09-05 at 11:53 +0200, arnaud gaboury wrote: > On Fri, Sep 4, 2015 at 5:58 PM, Martyn Plummer <plummerm at iarc.fr> wrote: > > On Wed, 2015-09-02 at 20:49 +0200, arnaud gaboury wrote: > >> On Wed, Sep 2, 2015 at 7:35 PM, arnaud gaboury <arnaud.gaboury at gmail.com> wrote: > >> > After a few days of reading and headache, I finally gave a try at

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

Hi folks, I suspect this is a request for a sanity check than a bug report: I've been successfully compiling an optimised version of R for several years using the Intel compiler and MKL. I've just test-run the new Intel 15.0 compiler suite, and I'm seeing a few numeric failures that I don't see using the same build method with Intel 13.0. I've attached the output of

This may not be a proper question to ask here, however I don't find a better place to ask. I am testing Ubuntu Natty 11.04. I build R with Blas/Lapack linked to intel MKL. Everything works fine but when quitting R with q(), the R process won't quit, and the system monitor shows its waiting channel as futex_wait_queue_me. For example, with "make check", the process will halted