similar to: Fortran and R: F90

Hi all, (Originally posted to r-help) I'm porting a package that I've worked on for OS X to Windows. The package is written in F95 so I need to compile it with gfortran and link it with gcc4. I've been trying to build an R with gcc4 without luck so far. If there is a binary of such a thing info would be appreciated. This package requires a Makefile. My question is, how can I find

Hi all, I have Win XP and R 2.3.1 on my notebook. I would like to write a package which includes some Fortran 95 code. Interestingly, if I compile and link the simple file test90.f90 directly with g95 -c test90.f90 g95 -shared -o test90.dll test90.o then PE Viewer ( a dll viewer) shows me the right functions in the export table, hence I can use the dll in R. But as it should become part of a

Hi, I found some bottlenecks in my R code with Rprof. First I wanted to rewrite them in C, but a colleague keeps suggesting that I learn Fortran, so maybe this is the time to do it... I like to learn new languages and do it fairly quickly. I would appreciate the advice of others about these questions: 1) I hear bad things about Fortran. Sure, F77 looks archaic, but F90/95 seems nicer. Is it

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:

Hello! Has anyone successfully compiled F90 sources in R-package? I found the same question on r-devel list from 2002 and I wonder if there is any progress. I heard that g95 and gfortran can be usable. And one more thing. I have a program written in F90 and lets suppose that compiler is not a problem. I've read manual 'Writing R Extensions' and successfully loaded one F77 subroutine

Hello! Has anyone successfully compiled F90 sources in R-package? I found the same question on r-devel list from 2002 and I wonder if there is any progress. I heard that g95 and gfortran can be usable. And one more thing. I have a program written in F90 and lets suppose that compiler is not a problem. I've read manual 'Writing R Extensions' and successfully loaded one F77 subroutine

Is it possible to run Fortran 95 code from R? I don't think so, but hopefully someone can prove me wrong. Here is the test I tried: A little fortran 95 subroutine: subroutine allloc() real, dimension(:, :), allocatable :: a integer :: n n = 10 allocate(a(n,n+1)) end I then compiled: >g95 -c allloc.f >R CMD SHLIB allloc.o Here is what happens when I try to dyn.load it in R 2.1.0

Is it possible to run Fortran 95 code from R? I don't think so, but hopefully someone can prove me wrong. Here is the test I tried: A little fortran 95 subroutine: subroutine allloc() real, dimension(:, :), allocatable :: a integer :: n n = 10 allocate(a(n,n+1)) end I then compiled: >g95 -c allloc.f >R CMD SHLIB allloc.o Here is what happens when I try to dyn.load it in R 2.1.0

I am reading the manual sections illustrating how to call a Fortran subroutine from R. I feel uneasy at the explicit statement about ".Fortran" interface working with Fortran 77. I would like to call a Fortran-90 subroutine from my R script. Is that supported at all ? Thank you, Maura tutti i telefonini TIM! [[alternative HTML version deleted]]

Hi, did anybody manage to compile F90 sources in an R-package? The major problem is, at least in my opinion, that non of the "free" F90 -> F77 converters is working correctly, at least for the F90 sources I need to compile. Torsten -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read

Hi, All, I have come across a problem building a DLL from .f90 source (R 2.3.1, Windows XP). When using the R CMD SHLIB procedure, the DLL itself was being built, but its export table was empty. Among the output from R CMD SHLIB the following message appeared: c:\mingw\bin\nm.exe: 'a.out': No such file The reason is the empty list of dependencies in the pattern rule for DLLs

Hi all, I have a working package for linux, including fortran 95 code compiled with g95, that I need to port to OS X. The package works on Linux and seems to load on the Mac, but when I try to run a function that calls C or Fortran I'm told that the symbol is not loaded. I'm developing via a shell account on an OS X system, I don't have access to a desktop. The set up is: R

We have a user here who is attempting to compile a package which requires f90 (gfortran will do). Our version of R was built with f77 (g77). When the user attempts to build the package, f77 is always invoked and fails due to the presence of f90 features. Is there a simple method or some documentation on how to force a package build to use a different compiler than the one used in

From the configure output of the latest devel snapshot: > checking for g77... no > checking for f77... no > checking for xlf... no > checking for frt... no > checking for pgf77... no > checking for fl32... no > checking for af77... no > checking for fort77... no > checking for f90... no > checking for xlf90... no > checking for pgf90... no > checking for

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

Dear LLVMers, Does anyone know what the latest is w.r.t a FORTRAN front-end for LLVM? Is anyone expecting to have typical f90/f95 programs compiling to LLVM this year, or next? (I'm aware of the "NAG hack" and various other f2c-type approaches, but they give me a strange feeling in my tummy.) Duraid

I have been revising some FORTRAN 77 routines in R packages I have previously submitted. Since R is now using gfortan I experimented with some Fortran 90 code (array intrinsics primarily). So far the code is still in F77 fixed format, in files suffixed .f (not .f90), but incorporates some F90 constructs. It has worked fine in linux/R. I tried to follow the thread of previous discussions

I am trying to load a .so file and get the following error message: > dyn.load("taper.so",local=F) Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library "/home/hpc1367/runs/taper/taper.so": ld.so.1: /usr/local/lib/R/bin/R.bin: fatal: relocation error: file /home/hpc1367/runs/taper/taper.so: symbol f90_init: referenced symbol not

Hello, I work under windows xp and I am trying to build a R package with a subroutine written in fortran 90. I have installed all the updated tools and I am working with R-2.4.0 or R-2.5.0. When I check a package with a subroutine in fortran 77 (and extension f) everything is ok. When I try to build the same package with a subroutine in fortran 90 (with extension f90) the following warning

Hi Chris, > > I use NAG with llvm-gcc4. What sort of errors do you get? Did you > configure llvm-test with the appropriate flags to find it? > Yes, I did. llvm-test is configured as follows: (in /work/LLVM/1.8/ llvm/project/llvm-test): ./configure --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec -- without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/work/