similar to: Problems using external BLAS

Dear developeRs, I'm trying to build R (2.7.1, on an x86_64 running Linux, but I believe I have observed this on x86 and with earlier versions of R as well) using external BLAS and LAPACK libraries _and_ generating libR.so, libRblas.so and libRlapack.so. Without --enable-BLAS-shlib, configure is able to find and use the external LAPACK library: ./configure \

I would like to build R and packages with the Intel 10.1 compilers in RHEL4. Using the flags below, I can successfully build R using a vanilla ./configure, but when I install new packages they build with gcc. My sysadmin suggested adding the flags to ./configure as illustrated below, but then the R build blows up with the config tail output that follows far below. It looks like gcc is still being

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

Hi all, I'm trying to build R from subversion with MKL 10.0.2 on Ubuntu. I tried: ./configure --with-blas='-L/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lguide' --with-lapack='/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lmkl_lapack' --enable-R-shlib and got: R is now configured for x86_64-unknown-linux-gnu Source directory: . Installation directory: /usr/local

Hi all, I'm trying to build R from subversion with MKL 10.0.2 on Ubuntu. I tried: ./configure --with-blas='-L/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lguide' --with-lapack='/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lmkl_lapack' --enable-R-shlib and got: R is now configured for x86_64-unknown-linux-gnu Source directory: . Installation directory: /usr/local

NO Hi. I'm not sure if this is an R-help or R-devel problem, so I'm starting here in the hope that someone can help (and willing to go to the other list if it's more appropriate). I think I am following all of the instructions in the various manuals, but clearly I am missing something. I have an Intel EM64T Dell with 2 dual-core Xeon processors running Red Hat EL5. I would

And here's a patch for Intel Math Kernel Library. This allows commercial users of Speex to use a high-speed FFT library that isn't GPL'd. (You do need to pay for it though). This is 3 times faster than the default FFT in speex, and also faster than FFTW3 since MKL has native support for the complex packing Speex uses. Since Intel hasn't supplied any pkg-config files, and which

Guys, I'm using a Linux PC (Pentium IV, Mandrake 10.1) and I've just tried to compile the new R-2.1.0 release with both gcc/g77 (3.4.1) and icc/ifort (8.1). Of course everything went fine with the GNU compilers. After checking the archives of the mailing list I tried compiling with the Intel compilers using the following options: CFLAGS = '-O2 -mp -prec_div' CXXFLAGS =

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,

I've been updating the information on tuned BLAS for R-admin in R-patched and R-devel. We have ATLAS (widely available, including for Windows) MKL (licensed on ix86 and x86_64 Linux and Windows) ACML (by AMD, but for all ix86 and x86_64 chips, Linux and Windows. Now available for gfortran.) Goto (academic use only, only some chips, only Linux) MKL and ACML provide full LAPACK,

dear experts I'd like to ask you, probably on behalf all of us who try to use AMD's ACML for performance optimisation a question. There seem to be problem when these two, R and ACML are coupled, described here: http://devgurus.amd.com/message/1255852#1255852 I'd like to ask, while not being a programmer/developer, how incorrect and dangerous this might be? maybe such a setup must

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

Normally, I do the following to configure R for compilation on my Opteron box with ACML installed: ./configure --with-tcltk --with-blas="-L/opt/acml4.3.0/gfortran64/lib -lacml" However, when I do so, and look at Makeconf, I see BLAS_LIBS = -lblas I thought I would see BLAS_LIBS = -L/opt/acml4.3.0/gfortran64/lib -lacml Why isn't Makeconf picking up the right BLAS_LIBS (or is

As a few of you will know, Dr Goto's BLAS is now available again (http://www.tacc.utexas.edu/resources/software/software.php), but only for academic use and only for Linux (at least in binary form, and source-code licenses are not yet available). http://www.netlib.org/lapack pointed me to AMD's ACML (http://www.amd.com/acml). This has a less restrictive licence, and seems at least

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

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 - 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,

While I recently received some very helpful files and email from Kevin Hendricks for compiling with ATLAS, thought I'd first have a stab at ACML. Having problems, which I suspect are trivial to solve: 1. machine is running RHEL 4, meaning, it uses gcc 3.4.5 out of the box, and g77. In my experience, over-riding RHEL's choice, and manually upgrading to gcc 4.x.x (and, as a consequence

Hi Tomas, Thanks for your reply. I find your response curious, however. Surely the identical() test is simply incorrect when catering for possibly different BLAS implementations? Or is it the case that conformant BLAS implementations all produce bit-identical results, which seems unlikely? (Sorry, I am unfamiliar with the BLAS spec.) Although whatever the answer to this theoretical question,

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