similar to: gfortran Makefile for windows

Hi all, I'm porting a package that I've worked on for OS X to Cygwin/Windows. This package requires a Makefile. My question is, how can I find out (or what is), the link command? Here is the OS X Makefile: RLIB_LOC=${R_HOME} F90_FILES=\ class_data_frame.f90 \ class_old_dbest.f90 \ class_cm_data.f90 \ class_cm.f90 \ class_bgw.f90 \ class_cm_mle.f90 \ cme.f90 FORTRAN_FILES=\ dgletc.f

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

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: We're trying to install the Hmisc package on a Solaris 9 machine. Here's what we get: R CMD INSTALL /usr/local/srctree/Hmisc_3.4-2.tar.gz * Installing to library '/usr/local/lib/R/library' * Installing *source* package 'Hmisc' ... ** libs g95 -fPIC -g -O2 -c cidxcn.f -o cidxcn.o g95 -fPIC -g -O2 -c cidxcp.f -o cidxcp.o g95 -fPIC -g -O2 -c hoeffd.f -o

In the odesolve routine lsoda(), I allow the function (named func) that calculates the system of differential equations to be defined in a dll that has been dynamically loaded from the file named in dllname. I use getNativeSymbolInfo(func, dllname)$address to get the address of the function and pass it to a C function called via the .Call interface. Inside that C function, I use

Hi, I need to create a Makefile.win for a given package so as to fiddle slightly with the compilation process. My Makefile works fine in Linux but I am having trouble creating Makefile.win for MinGW. I first looked at the commands that Rcmd SHLIB appeared to be running and copied those onto the Makefile. But one step seems to be missing, the creation of the _res.rc file needed by windres

Colleagues, I am preparing scripts that will be used by others on both Windows and Linux/OSX platforms. The scripts call an existing Fortran application. The user may have any of a a variety of Fortran compilers - my goal is to determine whether or not the test command returns "no input files" or "command not found" (i.e., so that I can confirm which Fortran they

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

Hello, I've been playing around w/ the new dynamic C symbol stuff (thank you for doing that!) in the, um, 5/11/01 R-devel package and, unless I've missed something incredibly obvious, there doesn't appear to be a mechanism for registering functions of an embedding executable. It seems like this would be a Good Thing to have. Since I'm doing most of my work in Windows at the

I'm sorry for having to post this, but I've run out of ideas. I've been trying to build R-2.8.1 from source for installation on FreeBSD 6.4 (seems to be working fine on osx) and keep getting the same results, regardless of how I set ./configure $ ./configure --enable-R-shlib --with-x=no --with-blas FFLAGS="-fpic" R is now configured for x86_64-unknown-freebsd6.0 Source

Another option might be g95 instead of gfortran. I haven't used it for a while, but I seem to recall it working fine in gcc 4.0.1. On 9/11/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/9/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > > On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote: > > > On 9/9/06, Chris

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

On 9/9/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote: > > On 9/9/06, Chris Lattner <sabre at nondot.org> wrote: > > > On Sat, 9 Sep 2006, Steven Bosscher wrote: > > > > You wrote: > > > >> The NIST F77 test suite doesn't seem to be compatible with

Hi, I have gnuwin32 (b18) and the rw0613b.zip version of R. With regards to (re)making the dynload dll demo given (zero.dll) could anyone tell me what the command line for the makefile should be. ie, make -f Makefile.in ...? Thanks for any help -- Douglas -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read

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

When I try to load winelib dll I get an error message: "err:module:MODULE_LoadLibraryExA Loading of native DLL <dllname> failed (error 193), check this file." The error message is printed for call: DllHandle = LoadLibrary(DllName); This happens even when I try to load standard Wine dlls, like dlls/msisys.ocx.so Did I miss something obvious? Thanks, Andriy Palamarchuk

Hi, I'm having a problem using the 'SHLIB' command in R. I keep getting syntax errors. The help gives the following usage for it: Rcmd SHLIB [-o dllname] files 'files' is supposed to be a list of files, but whether I set up a list or a character vector, I still get a syntax error. Does anyone know if they're are supposed to be quotes somewhere in there? If someone has an

Hello, I wanted to test the odesolve package and tried to use compiled C-code. But when I do: erg <- lsoda(y, times, "mond", parms, rtol, atol, tcrit=NULL, jacfunc=NULL, verbose=FALSE, dllname="mond", hmin=0, hmax=Inf) I get the error message: Error in lsoda(y, times, "mond", parms, rtol, atol, tcrit = NULL, jacfunc =