search for: libacml_mp

...ATH is set... I set it in /etc/bash.bashrc (is that ok?) and it shows up when I echo $LD_LIBRARY_PATH I also tried adding the paths to the ld.so cache as Prof Ripley had suggested. I get the same results when running configure. So after that I decided to try and replace libRblas.so with a link to libacml_mp.so. I ran a regular configure command followed by a make, then added the link. I now have this in my R lib folder... lrwxrwxrwx 1 root root 46 2010-08-25 09:20 libRblas.so -> /opt/acml4.4.0/gfortran64_mp/lib/libacml_mp.so* Is there any way I can verify that it is using this libacml_mp...

...-lm >&5 conftest.c: In function 'main': conftest.c:193: warning: implicit declaration of function 'dgemm_' configure:28588: $? = 0 configure:28595: result: yes configure:29120: checking whether double complex BLAS can be used ./conftest: error while loading shared libraries: libacml_mp.so: cannot open shared object file: No such file or directory -- View this message in context: http://r.789695.n4.nabble.com/Trouble-configuring-R-to-use-ACML-tp2337193p2337193.html Sent from the R help mailing list archive at Nabble.com.

...d R > > If one has a different BLAS shared library on my system, one does not > recompile. Rather move R's libRblas.so and then make a symlink from > the new shared BLAS to where the old one was. > > The doc has this example: > > ln -s /opt/acml4.4.0/gfortran64_mp/lib/libacml_mp.so R_HOME/lib/libRblas.so > > So I'd just have to figure out which shared library is the right one > and put it where libRblas used to be. > > Here's what I don't understand about the current R packaging. > > In the deb packages, I download from CRAN, there is n...

So, tried again from scratch. Again, CentOS 5.3, which is essentially RHEL 5.3. ./configure --with-blas="-L/opt/acml4.3.0/gfortran64/lib -lacml" In config.log, get things like configure:37199: checking for dgemm_ in -L/opt/acml4.3.0/gfortran64/lib -lacml configure:37230: gcc -std=gnu99 -o conftest -g -O2 -I/usr/local/include -L/usr/local/lib64 conftest.c

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