similar to: config.log told me to report these (PR#12035)

Recently I posted to this list with a question about using the Intel 10.1 compilers in building R and one response was basically, "why in the heck would you want to do that?" The answer is that my sysadmin believes that there will be a performance boost with the Intel vs. Gnu compilers on our Linux cluster, of which I am one of many users. Wanting to be a good citizen and use my machine

I'm compiling the latest stable build (2.7.0) from source using the Intel Compilers, following the hints in the R-admin guide. I'm using OpenSUSE 10.3 on a Intel Q6600 system. First let me explain a few things I did: 1: Download & Install all the Intel Compilers (as well as the Intel Math Kernel Library) (All defaults) 2: Set up my environment variables in profile.d, using the handy

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 =

I am having trouble compiling R-2.6.2 on suse linux x86_64 using the intel compiler. I read section C.2.1 Intel compilers in the R Installation and Administration manual, and put CC=icc CFLAGS="-g -O3 -wd188 -ip" F77=ifort FFLAGS="-g -O3" ICC_LIBS=/opt/intel/cce/10.1.012/lib IFC_LIBS=/opt/intel/fce/10.1.012/lib/ LDFLAGS="-L$ICC_LIBS -L$IFC_LIBS -L/usr/lib64"

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

Full_Name: Reinhold Bader Version: 2.1.0 OS: SLES 9 Submission from: (NULL) (129.187.48.1) I tried to build R using the Intel compilers (icc, ifort) and the Math Kernel Libraries for BLAS/LAPACK Optimizations used were -O3, and the FPICFLAGS="-fpic" was exported. The build failed with the following error message: ... dumping R code in package 'methods' Saving namespace image

Hi, I am running Linux (64 bit) R, compiled under gnu compilers. I am looking to compile a Fortran program with the ifort (the intel compiler) and then be able to import that as a library into my version of R. I am using the flags FC=ifort and SHLIB_FCLD=ifort, however ifort does not seem to recognize the libR.so file. Does any one have experience with this/know of a a way to load an ifort

I have access to a cluster on which I have been supplied with R 3.1.0 which appears to have been built using the intel compiler tools. The following minimal Fortran file: subroutine truth(lind) logical lind lind = .TRUE. end Compiles thusly: arcadia> R CMD SHLIB truth.f ifort -fpic -O3 -xHOST -axCORE-AVX-I -fp-model precise -c truth.f -o truth.o ifort: command

Sorry for the long letter! I have recently started using R. For the start I have tried to repeat examples from Milliken & Johnson "Analysis of Messy Data - Analysis of Covariance", but I can not replicate it in R. The example is chocolate chip experiment. Response variable vas time to dissolve chocolate chip in seconds (time), covariate was time to dissolve butterscotch chip

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, I am having problem building R 2.10, and it does not seem anyone else is having a similar problem... My system information: uname -m = x86_64 uname -r = 2.6.31-ARCH uname -s = Linux gcc (GCC) 4.4.1 icc (ICC) 11.0 20081105 The first problem I encounter seems to be with icc and wctype.h during ./configure. export CC="icc -std=c99" export CXX=icpc export OBJC="icc

Can anyone tell me if there exists an rpm for netcdf-3.6.0-p1 for Centos x86-64? Also, are there any details of what was used to compile it, i.e., ifort, pgf, g77, etc. I'm looking for a version compiled with ifort... Sam -- Snowman

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

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

Full_Name: Danny van Dyk Version: R-2.2.0 OS: Gentoo/AMD64 Submission from: (NULL) (83.129.50.65) I have successfully compiled R-2.2.0 using ifc-9.0.026 on my x86_64 box. The only (minor) change that hade to be made was adding fpicflags="-fPIC" to configure.ac in case F77 matches either "ifc" (old name) or "ifort" (new name). Please apply following patch: dvandyk

Full_Name: Christian Marquardt Version: 2.2.1 OS: Linux Submission from: (NULL) (84.167.229.240) Hello, I believe this is a bug in the configuration / installation: When configuring R-2.2.1 using the Intel v9 Fortran compiler as default Fortran compiler and g++ as C++ compiler on a Suse 9.3 Linux, the configuration script finds that the C and Fortran idea of double comples disagree. I have

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 :

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

>>>>> Wim R Cardoen writes: > Hello, > I experienced a compiler error when I tried to compile the latest version > of R i.e. R4.0.2 > making iosupport.d from iosupport.c > making lapack.d from lapack.c > making list.d from list.c > making localecharset.d from localecharset.c > grep.c(74): catastrophic error: cannot open source file "pcre2.h" >