similar to: more on make check states failure

For grins, tried rebuilding R 2.9.0 without using ACML 4.3.0. Config goes fine, make runs without any errors. make check - and - ta-dah! - no errors for stats. Everything seems to check out just fine. So, it seems as if R 2.9.0, ACML 4.3.0, and perhaps one/more things under CentOS don't play nice. Will trying unloading 4.3.0, installing 4.2.0 (which worked before on the Fedora box), and

Quick followup. Confirmed that TCl/Tk are both installed on the machine (they are, in both 32- and 64-bit flavours), as are all tcl and tk-related libs, devel packages, and about everything else I could find. It occurred to me that perhaps the R I compiled isn't 'tcltk' aware. I checked the config.log, and there is some hint that this might be the case. Just before ## File

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

Dear all, I encountered a problem when compiling the source of R patched 2.10.0 r50499 (19-11-2009) linked to ACML single threaded (4.2.0 or 4.3.0) OS: openSuSE 11.0 x86-64 make fails when it comes to installing mgcv with the following [snip] ** R ** inst ** preparing package for lazy loading Error in loadNamespace(i[[1L]], c(lib.loc, .libPaths())) : non esiste un pacchetto chiamato

So, I tried the following configure: ./configure --with-lapack --with-blas --with-tcltk No use of ACML at all, but both lapack and blas. Configure proceeds without any errors. Make, same thing. Make check - same problem with stats. But, this time a .fail file got created in tests/Example. Bottom of the file has something which might resonate with someone out there: Error in La.svd(x, nu,

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,

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 handle SysAdmin for a multi-user Linux box, with R 2.7.1 compiled and installed to make usee of ACML (Opteron chips). The library files (packages) are installed to /usr/local/lib64/R/library Everything works as it should, except for the following. Say I have a user (an R developer) who has developed a package called Blaster. We'll call the user guru. Now, /home/guru/Blaster, contains the

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

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

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

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

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

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

Hi, I'm following up to a post I made to r-help here: http://r.789695.n4.nabble.com/Trouble-configuring-R-to-use-ACML-tt2337193.html#a2337193 I have verified that LD_LIBRARY_PATH 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

Hi, Has anyone had any luck in using portland group compiler to build R(-devel) with AMD's pgi compiled ACML library? I've downloaded the packages and set LD_LIBRARY_PATH, and run configuration script as follow: % ./configure --prefix=/usr/local/R.pgcc --with-blas='-lacml' However, it failed to pick up double complex BLAS, checking for sgemm_ in -lacml... yes checking

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