similar to: How to get R cmd to check Fortran array bounds

Hi I've built a dll using Fortran code and can call it by either R or Fortran. Calling by the former gives me the wrong answer and the later gives the correct answer. >From what I've read, it looks like I should use the subroutines DBLEPR, INTPR and REALPR to print to the R console rather than using Fortran standard I/O and that if I use the command R CMD SHLIB source.f that these

I previously sent a cri de coeur about this problem to the r-help list but so far have not managed to extract a solution. So I am trying here. (Uh, Ubuntu *is* a "special instance" of Debian, isn't it?) The problem is that I cannot install rgdal, and I need it. Rather desperately. I do: install.packages("rgdal",lib="/home/rolf/Rlib") and get the error

Hi Nuno, I noticed your commits related to -fbounds-checking and have some questions. The functionality of this new phase seems to (partially?) overlap with AddressSanitizer and SAFECode, so I am curious how would you compare the two existing tools with the new one. Earlier you wrote: >> So the main idea of this new flag is not for debugging, but rather for production. >> This means

Hello! I have some Fortran code that uses BLAS calls, and would like to compile it into a shared object to call it from R as per the "Writing R Extensions" manual. What needs to go into the "Makevars" file, so that running the R CMD SHLIB will work in Ubuntu? The code compiles properly on the Mac, with the Makevars line PKG_CFLAGS=-Wl,-framework -Wl,vecLib but of course

I am running into the following issue that has been previously reported on the R-devel mailing list. The short version is that I'm writing a package for MPI, and I'd like to change CC and SHLIB_LD to "mpicc". Trying to change them in Makevars.in has no effect, because the values are clobbered by /etc/R/Makeconf. Will the following changes to Makeconf.in introduce any problems?

Hi I've built a dll using Fortran code and can call it by either R or Fortran. Calling by the former gives me the wrong answer and the later gives the correct answer. From what I've read, it looks like I should use the subroutines DBLEPR, INTPR and REALPR to get values to show up in R which I hope will allow me to find the error. I've downloaded the R-2.12.0.tar.gz but have

I got this to work on Linux but it is not working on Windows. *My understanding is that this should also work on windows, is that correct?* If so, what should I do? differently? To get it to work on Linux, I modified my R script as follows: #' OpenMP Hello World #' #' @param nthreads The number of threads that you want to use #' @example #' hello(nthreads=2) #' @export

Hi, I recently managed to port the slicot library (http://slicot.org/) to R. I created a new package, put the fortran libs into the src directory together with a Makevars file that include the line: PKG_LIBS=$(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) R CMD check did run through on my ubuntu 14.04 64bit machine with 1 warning and 4 notes. Now I wanted to create a Windows version of that package by

Hi everybody, I'm trying to develop an R package with Fortran and OpenMP. I wrote a simple hello world but I'm not able to set the number of threads. I found this old email chain <http://r.789695.n4.nabble.com/Set-the-number-of-threads-using-openmp-with-C-td2284685.html> and I tried to set my compile instructions accordingly but i had no luck. *This is my makevars:*

To all. I need your help. The big question is: How do I make an R library with Fortran 95 files? You may assume that I am a pretty decent programmer in both R and Fortran. I lay out a scenario and need your help! I know how to make an ordinary R package and have dabbled with R + Fortran 95 *.dll linking. I do not have a great handle on the whole Makevars file and whatever else I might need

Hello I'm trying to run a fortran code which use LAPACK subroutines. I think I should use some points shown in the manual 5.5 Creating shared objects but it is too technical for me :-(... Could anyone help me for the procedure to do: -which part of the manual is relevant for this type of question? actually I'm speaking from writing R extensions, should I read R admin? -point 1.2

I built my package under the R version 2.14.1 on windows without any problems by first checking for issues using R CMD check (no warnings) and then R CMD build to build the tar.gz. I can install this on version 2.14.1 using install.packages(...). I next tested to see if I could also install on version 2.15.0 (also on my computer) using install.packages() with the version 2.14.1 tar.gz this

Hi, I wonder about the reason for the following lines: $ diff ~/local/lib64/R/bin/build /usr/lib64/R/bin/build 40c40 < my $revision = ' $Rev: 46832 $ '; --- > my $revision = ' $Rev: 45803 $ '; 576,579d570 < if(-r "Makevars") { < $makefiles .= " -f Makevars"; < R_system("${R::Vars::MAKE}

Le 27/09/16 ? 13:31, Dirk Eddelbuettel a ?crit : > > On 27 September 2016 at 09:37, Eric Deveaud wrote: > | Hello, > | > | I'm tring to install a Rpackage that holds some C//C++ code > | > | as far as I understood the R library generic compilation mechanism, > | compilation of C//C++ sources is controled > | > | 1) at system level by the ocntentos

I am just trying to adjust one of my packages so the C code builds in Windows. This is code that has been around for a long time, and I'm am only a casual reader of C, so it has had the "if it is not broken don't touch it" approach for many years. The section 1.2.1 "Using Makevars" of "Writing R extensions" starts: "Sometimes writing your own

Hi All: I get the following error when trying to install the rjags package. I've installed the jags software and I'm using Fedora 10.0 and my sessionInfo is at the bottom of this email. I'm also sorry if this email ends up having control A's all over it. I still haven't figured how to fix that. Thanks. [1] "LOADING MASS LIBRARY" checking for

Hi there, I'm having trouble to compile the R + C/C++ codes for this project from Yahoo folks on latent factor models: https://github.com/yahoo/Latent-Factor-Models#readme After downloading the package from the site, I could not successfully *make* the files. Here is the message: ====================================================================================== sh-4.1$ make R CMD

Hello, I'm tring to install a Rpackage that holds some C//C++ code as far as I understood the R library generic compilation mechanism, compilation of C//C++ sources is controled 1) at system level by the ocntentos RHOME/etc/Makeconf 2) at user level by the content of ~/.R/Makevars 3) at package level by the content of src/Makevars Problem I have is that src/Makevars is ignored see

On 5/24/12 4:43 AM, Kostya Serebryany wrote: > Hi Nuno, > > I noticed your commits related to -fbounds-checking and have some > questions. > The functionality of this new phase seems to (partially?) overlap with > AddressSanitizer and SAFECode, > so I am curious how would you compare the two existing tools with the > new one. Nuno's original goal (described in our

I'm trying to build a package which has both gfortran and c++ code. In my installation of R, the R CMD INSTALL process compiles each c++ and gfortran code with the correct compiler, but performs the link step with "gfortran" and this creates undefined symbols at load time. How does one override/force the use of a different command in the link step? Is there an appropriate entry