similar to: [PATCH] Add fpicflags for Intel(R) Fortran Compiler (PR#8344)

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

Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.

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

Hi, I'm a sysadmin who's been tasked with installing R on our 1000-node compute cluster. I have licences for the Intel C and FORTRAN compilers, so I'm using the following to compile: CFLAGS="-O2 -axWK" FFLAGS=$CFLAGS CXXFLAGS=$CFLAGS CC=icc F77=ifort CXX=icc FPICFLAGS=-fpic ./configure --without-x --without-tcltk The compilation seems to go OK, with a few warnings.

I have gotten this error while attempting to build R-2.13.2 and R-2.14.0 using ./configure --with-x=no --enable-R-shlib, and ./configure --with-x=no Red Hat Enterprise Linux Server release 5.6 (Tikanga) ========================= Warning in solve.default(rgb) : unable to load shared object '/users/home/mked/R-2.13.2/modules//lapack.so': /users/home/mked/R-2.13.2/lib/libRlapack.so:

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

Hello, I am trying to build the R-2.11.1 software for university faculty to use in research projects on a DEC/Compaq/HP AlphaServer model GS160 16CPU/64GB memory running Tru64Unix aka OSF1 version 5.1B-5. Is it known whether it is possible to build the R-2.11.1 software on the platform I am using? In my attempts to build the R-2.11.1 software, I first used the native C and Fortran 77/90/95

Greetings, I'm attempting to install R-0.64.1 on a Sun Sparc 20 running Solaris 2.4 with gcc-2.7.2.2, g77-0.5.20 and Gnu make 3.76-1. On several occasions, the make process aborted when trying to build the shared object file for the modreg package (its first attempt at such a beast). In all attempts, the error message is as follows: ../../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o

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

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

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

On Linux x86-64 (Ubuntu 6.06), the latest R sources from the Subversion trunk fail to build with the following "recompile with -fPIC" error: $ ./configure --with-x=yes --prefix=$inst_dir --enable-R-shlib --with-tcltk=/usr/lib/tcl8.4 --with-tcl-config=/usr/lib/tcl8.4/tclConfig.sh $ make /usr/bin/ld: ../appl/approx.o: relocation R_X86_64_32 against `a local symbol' can not be

Hi, I have downloaded rstp from sourceforge and I get a segfaults when running the daemon. This is the line where the problem arises: TST(ifc->master->stp_up,); just at the beginning of function: void bridge_bpdu_rcv(int if_index, const unsigned char *data, int len) in file bridge_track.c -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Hi!! I found your ipconfig stuff in the udev rpm in SuSE 9.1. I'm about to setup a initramfs (pretty cool - much better than initrd) to boot linux diskless clients over the net. All the tools I would need, seem to be there with ipconfig/nfsmount ... I like to use the information I get from PXE/syslinux or Etherboot writing something like:

Hello, I am trying to install R on Suse linux 10.1. To get configure to run correctly, I had to set FPICFLAGS=fPIC. R is now configured for i686-pc-linux-gnu Source directory: . Installation directory: /usr/local C compiler: gcc -std=gnu99 -g -O2 Fortran 77 compiler: g77 -g C++ compiler: g++ -g -O2 Fortran 90/95 compiler: g77 -g

Full_Name: Sigbert Klinke Version: 2.1.1 OS: Suse Linux 10.0 (Full DVD) Submission from: (NULL) (141.20.100.252) Suse 10.0 installs only a Fortran 95 compiler with g77 compability mode. Using this leads in "configure" to an abortion with problems about "FPICFLAGS". Deinstalling g77 compatiblity mode, using f2c, compiles R. But after calling R() the program shows its entrance

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

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