similar to: compiling 2.6.2 using icc

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

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

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 advices and hints. OS: Fedora 22 parallel_studio_xe_2016 Hardware : 8 Thread(s) per

Hi all, I have the issue: icc -std=c99 -std=gnu11 -I../../src/extra -I../../src/extra/xdr -I. -I../../src/include -I../../src/include -I/usr/local/include -I../../src/nmath -DHAVE_CONFIG_H -fopenmp -fpic -g -O3 -wd188 -ip -mp -c eval.c -o eval.o arithmetic.c(66): warning #274: declaration is not visible outside of function int matherr(struct exception *exc) ^

Note that 'intel 2022' is a bit vague. The current version is 2023.1.0, and that has both the 'classic' (icc/icpc/ifort which it seems you used) and new (icx/ixpx/ifx) compilers -- the former are said to be going to be discontinued later this year. R did not know about ifx so did not build with the new set. The parts of the manual Tomas referred to were about the old

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

Hi, I'm encountering trouble compiling caTools_1.17.1.tar.gz and e1071_1.6-4.tar.gz on a Linux system using the Intel compiler suite. 14 other packages I generally use installed without any trouble. I notice both of these trouble packages have a C++ component, so I wonder if that might be the issue. Below, there's information on my platform, compiler, and some diagnostic output showing

Hi Martyn, Thanks for your insight, that seems pretty direct. Unfortunately, I did not compile this version of R (it's on a large supercomputer system and this version of R was installed by the admins). Using "R CMD config", I see the following relevant settings: DYLIB_LD = icc -std=gnu99 DYLIB_LDFLAGS = -shared -openmp LDFLAGS = -L/opt/compilers/intel/cce/9.1.039/lib

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

I want to build R optimized, with either MKL, OpenBLAS or ATLAS. My OS: Fedora 22 Hardware: CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 Thread(s) per core: 2 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz I am a little confused when it comes to choose a method and would like to hear your experiences. If I am right, I have 3 possibilities: -

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 website (indeed, there?s some mention of successful past builds, and the

A couple of years ago (in 2008, using R 2.7.x, I believe) I noted that using the configure switch --enable-R-shlib when buildig R made configure ignore any specified external LAPACK library and use the internal one insted. I asked why, and was told it was intentional. Now, with R 2.15.1, I see that it at least appears that this is no longer the case. I've run configure like this:

A couple of years ago I noted that using the configure switch --enable-R-shlib when buildig R made configure ignore any specified external LAPACK library (I cannot recall if also the BLAS specification was ignored) and use the internal one insted. I asked why, and was told it was intentional. Now, with R 2.15.1, I see that it at least appears that this is no longer the case. I've run

On Tue, 2015-04-21 at 11:46 -0600, Andy Jacobson (NOAA Affiliate) wrote: > Hi, > > I'm encountering trouble compiling caTools_1.17.1.tar.gz and > e1071_1.6-4.tar.gz on a Linux system using the Intel compiler suite. > 14 other packages I generally use installed without any trouble. I > notice both of these trouble packages have a C++ component, so I > wonder if that might

On Mon, Aug 24, 2015 at 11:29 AM, Bj?rn-Helge Mevik <b.h.mevik at usit.uio.no> wrote: > arnaud gaboury <arnaud.gaboury at gmail.com> writes: > >> - Intel MKL: this is part of Intel Parallel Studio and is a paid >> software. Now, there is the MKL package distributed by >> Revolutionanalytics, but I am not certain how this can be distributed >> for free. Is

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 =

Hi, I got the following problem when I type make. The error is not enough verbose to me so I can find the problem. Please cc me, I'm not subscribed. Thanks, Mathieu --------------------------- make[4]: `vfonts.so' is up to date. building system startup profile building package 'base' all.R is unchanged ../../../library/base/R/base is unchanged dyld: lazy symbol binding failed:

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