similar to: R CMD SHLIB with ifort

Hi, i have been running R 2.11 compiles with the goto blas libraries successfully for about a year. I am running Ubuntu 10.10 64 bit. However, recently I have been periodically getting a segfault when running R (and numpy -- also compiled against goto blas). When I check the dmesg error log I get the following message R[28792]: segfault at 7f4183ed4000 ip 00007f4196f05f03 sp 00007f4192d55d20

Hi, I am trying to use the merge command in the data.tables package. However, when I run the command I am not sure if it is running the merge command from the base package or the merge command from data.tables. When I run "methods(generic.function="merge")' it informs me that 'merge.data.table" is "non-visible". I am just trying to run the merge command on two

Full_Name: Lukasz Andrzej Bartnik Version: 2.8.1 OS: RHELS 5.2 Submission from: (NULL) (194.181.94.250) Compile R for 32 bit on a 64 bit machine: unset LD_LIBRARY_PATH unset R_LD_LIBRARY_PATH export CC="gcc -m32" export CXXFLAGS="-m32 -O2 -g" export FFLAGS="-m32 -O2 -g" export FCFLAGS="-m32 -O2 -g" export OBJCFLAGS="-m32 -O2 -g" export LIBnn=lib

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

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

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

Hi. I'm trying to install a new package. I'm a relatively long-time (though not advanced) R user and have never seen this error before. For the first example, I tried a few different CRAN mirrors. In the second example, the file does exist; I downloaded it from the CRAN website for the package and pasted in the name exactly a few different times to make sure it was right. >

I have a question for our European readers: how common is it to use commas as decimal points in spread-sheet and statistics applications? Is it an inconvenience to require that all data use a period as decimal point? (i.e., 3.14159 rather than 3,14159). We're trying to make our program as foolproof as possible, and would prefer not to give users a chance to have commas as both decimal

Hello r-bugs, I am running openSuse 11.0, with my new Intel 8500 (Penryn) C2D, and I want to use icc and ifort. I was able to get a working Goto BLAS, following Dr. Goto's instructions. That seems to work OK with gcc and gfortran. I get about 10% faster computations by using -O3 rather than -O2. I get faster results with Goto BLAS rather than the R BLAS. Now I want to make icc and ifort

I want to eliminate certain observations in a large dataframe (21000x100). I have written code which does this using a binary vector (0=delete obs, 1=keep), but it uses for loops, and so it's slow and in the extreme it causes R to hang for indefinite time periods. I'm looking for one of two things: 1. A document which discusses how to avoid for loops and situations in which it's

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#

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

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

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" # include<pcre2.h> (The pcre2.h header file is actually present!) I used the

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

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

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 :