search for: jbremson

...'sym.add' the .Fortran call looks like this: .Fortran(symbol.For("add"),...) symbol.For works correctly if there is an underscore in the name though. I have tested this on OSX and linux and get the same results. I have a test package written up if anyone wants it. Email me at jbremson at wald.ucdavis.edu. --please do not edit the information below-- Version: platform = i686-pc-linux-gnu arch = i686 os = linux-gnu system = i686, linux-gnu status = major = 2 minor = 1.0 year = 2005 month = 04 day = 18 language = R Search Path: .GlobalEnv, package:foo, package:me...

...er :: 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 > dyn.load("allloc.so") Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library '/home/jbremson/dev/f_code/allloc.so': /home/jbremson/dev/f_code/allloc.so: undefined symbol: _g95_filename Is there any way to deal with this? Is it somehow possible to reach the fortran 95 through C and avoid this whole problem? Regards, Joel Bremson UC Davis [[alternative HTML version deleted]]

...er :: 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 > dyn.load("allloc.so") Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library '/home/jbremson/dev/f_code/allloc.so': /home/jbremson/dev/f_code/allloc.so: undefined symbol: _g95_filename Is there any way to deal with this? Is it somehow possible to reach the fortran 95 through C and avoid this whole problem? Regards, Joel Bremson UC Davis [[alternative HTML version deleted]]

...les as follows in bash: export PATH=~/bin/:$PATH export F77=gfortran export LD_LIBRARY_PATH=~/bin/irun/lib export GFORTRAN_STDIN_UNIT=-1 Now I'm trying to write a Makevars file for my test package and not quite sure how to do it. I've tried FF=gfortran GFORTRAN_STDIN_UNIT=-1 FLIBS=/home/jbremson/bin/irun/lib/libgfortran.a but when running an R CMD check on the package I see that it's still using g77 to compile: -----output---- ... ** libs g77 -fPIC -g -O2 -c estimate.f -o estimate.o estimate.f: In subroutine `estimate': estimate.f:20: forall (i = 1:nxrows) beta(i) = i * 2 ^ Inva...

...(FORTRAN_FILES:%.f=%.o) g95 -L/Library/Frameworks -o $@ $^ -L/Library/Frameworks/R.framewo\ rk/Resources -----end makefile------------------------ Here is the relevant output of R CMD CHECK: * checking for working latex ...sh: line 1: latex: command not found NO * using log directory '/Users/jbremson/dev/bpkg.Rcheck' * using R version 2.1.0, 2005-05-12 * checking for file 'bpkg/DESCRIPTION' ... OK * this is package 'bpkg' version '1.0-1' * checking if this is a source package ... OK * Installing *source* package 'bpkg' ... ** libs g95 -c -g dbest_dbase_class...

..."add",as.numeric(a),as.numeric(b),c=as.numeric(0)) return(out$c) } > x = myadd(3,7) [1] 10 And you've done it! Be vanquished naysayers, simple addition will trouble us no more! (I thought a very simple tutorial on integrating Fortran code into R might be of use.) Joel Bremson jbremson@wald.ucdavis.edu Statistics Graduate Student UC Davis [[alternative HTML version deleted]]