search for: lmkl_lapack64

...ting libR.so, libRblas.so and libRlapack.so. Without --enable-BLAS-shlib, configure is able to find and use the external LAPACK library: ./configure \ --with-blas="-L/site/intel/cmkl/8.1/lib/em64t -lmkl -lvml -lguide -lpthread" \ --with-lapack="-L/site/intel/cmkl/8.1/lib/em64t -lmkl_lapack64 -lmkl" \ --enable-R-shlib [...] External libraries: readline, BLAS(generic), LAPACK(generic) Additional capabilities: PNG, JPEG, iconv, MBCS, NLS Options enabled: shared R library, R profiling, Java However, if I add --enable-BLAS-shlib, the external LAPACK will not...

...lly built older versions of R with MKL 8.1 earlier, but with intel compilers v. 10.1, using ./configure --prefix="/site/VERSIONS/R-$version" \ --with-blas="-L/site/intel/cmkl/8.1/lib/em64t -lmkl -lvml -lguide -lpthread" \ --with-lapack="-L/site/intel/cmkl/8.1/lib/em64t -lmkl_lapack64 -lmkl" \ --enable-R-shlib but we wanted to switch to gcc because not all R packages compile with icc.) Does anyone have any idea about what could be wrong? -- Regards, Bj?rn-Helge Mevik

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