similar to: Fortran level mismatch between package and R

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

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

I too have some messy F77 code that I'm considering porting to F90. BUT: Has anyone had luck creating shared-objects from F90 to load in R? What about submitting packages to CRAN with F90 code? BTW: I'm using the Intel compilers for Linux - free for Not-for-profit orgs. -R -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read

On Oct 30, 2008, at 11:02 PM, Chris Lattner wrote: > On Oct 30, 2008, at 5:23 PM, Jack Howarth wrote: >> ps We do have one oddity left in llvm-gfortran from current llvm >> svn. I find everytime I compile something with llvm-gfortran that >> I get a series of warning messages... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/

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, 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, We just got the Sun Performance Library for our Suns running Solaris 2.6, and I read the relevant section of the "R Installation and Administration Manual" about configuring R to use BLAS. The manual suggests you must use Sun's "cc" and "f95" (maybe "f90"?) compilers in order to use the Performance Library. We have "cc" but not

We have (spatial statistics) group here that are (about to) interface Fortran 90 and/or 95 software to R and/or S-plus. My recommendation has been against this because of non-availability of GNU or other free (not only moneywise, in the GNU sense) compilers for Fortran 9x. Does anybody have good guesses about the future here? The user group here say they like F 9[05] because of its ``object

When trying to build R-1.1.0, the configure script reported no Fortran compiler, even though '/usr/bin/f2c' was present, and R-1.0.1 had found and successfully used this. I traced this to an apparent typo in line 2067 of configure: for name in g77 fort77 f77 f90 xlf cf77 fc; do changing this to: for name in g77 fort77 f77 f90 xlf cf77 f2c; do allowed the script to 'find'

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

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

Greetings, We are trying to compile a 64bit version of R (1.7.0) on HP-UX (11.11), but are running into some problems. The following relevant filesets are installed: B3901BA B.11.11.04 HP C/ANSI C Developer's Bundle for HP-UX 11.i (S800) B3909DB B.11.11.60 HP Fortran 90 Compiler and associated products (S800) B3913DB C.03.33.01 HP aC++ Compiler (S800) This is our configure step:

Hi, working with R, version 0.63.0, I was successful to dyn.load fortran90 subroutines on a Solaris 2.6, as long as they are more or less in conformity with f77. It was not possible to work with statements like REAL,DIMENSION(:) :: d or x=SUM(y). REAL,DIMENSION(1:10) :: d is possible. We compiled R with f77. Is it possible with real f90 routines or is is in any conflict with the shared

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

Unless I force the Fortran compiler through --with-g77, configure fails to find and use the installed g77. I would submit a patch for configure.in, but I can't quite follow the logic in configure.in. $ ./configure creating cache ./config.cache [...] checking for main in -lm... yes checking for g77... /usr/local/gnu/bin/g77 checking for fort77... (cached) /usr/local/gnu/bin/g77 checking for

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

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

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