similar to: fortran into R

I get an error when trying to compile a FORTRAN source file for use in a package that I am developing. The error, reported in 00install.out is below. * installing *source* package 'USGSstats' ... ** libs *** arch - i386 C:/PROGRA~1/R/R-214~1.1/etc/i386/Makeconf:194: warning: overriding recipe for target `.m.o' C:/PROGRA~1/R/R-214~1.1/etc/i386/Makeconf:187: warning: ignoring old

Hi all, Thanks to everybody who thought on this problem, there was slight mistake in the fortran code which lead to NULL pointer allocation error, but still it surprises me that why it does not crib in the first run. The compiler I am using is absoft fortran compiler. Cheers, -Jag Jagadish Rangrej ( Statistician ) CHEO Research Institute, Ottawa, ON 613-7383951 > -----Original Message-----

Dear all, I'm writing a code that requires Bessel functions with complex argument. Searching the list, I found the continuation of a thread I initiated a few months ago: http://tolstoy.newcastle.edu.au/R/e4/devel/08/03/0746.html As I understand, the most promising option would be to use the fortran or C implementation of Amos,

Dear R users, I'm porting a piece of Matlab code to R, but I'm now stuck with the following: I need an equivalent of besselJ(x, nu) that can handle a complex argument x. I couldn't find any R implementation. I did find a possible fortran solution in SLATEC (< http://www.netlib.org/slatec/ > , CBESJ-C), however I've never tried to use external C or Fortran code

Dear R users, I'm porting a piece of Matlab code to R, but I'm now stuck with the following: I need an equivalent of besselJ(x, nu) that can handle a complex argument x. I couldn't find any R implementation. I did find a possible fortran solution in SLATEC (< http://www.netlib.org/slatec/ > , CBESJ-C), however I've never tried to use external C or Fortran code

Hello, I have been trying to use a collection of Fortran subroutines to return a 2D array of calculated values to my R code, calling a Fortran wrapper subroutine from R. I've done this successfully before with C & C++ code. The Fortran wrapper subroutine which is to be called by R takes a set of input arguments & then should return an array of 2 columns & the specified number of

Ben Bolker gives some reasons why Numerical Recipes may be problematic as a starting point for R codes. CUP did a masterful job of marketing, but the license is restrictive as the links he gives points out. In some tests, I've also noted that some of the algorithms are less than stellar e.g, convergence tests in one or two optimization routines. Should we have a wiki item to help people find

hi! I would like to know if it is feasible to use the dragon egg gcc plugin to automatically convert fortran code to c. Having found that it is possible to output llvm byte code back to c (at least something like this gave me this impression/hope: llc -march=c -o test.c) I am hoping to use dragon egg to generate the byte code from fortran 90 which than output to c. Does this seem feasible at

I successfully used .Fortran to load and execute my fortran procedures under WinXP and 32 bit R. Alas, the same isn't true with my next Windows 7/64 machine, R 2.14.1 (64 bit) and the gnu gfortran (64) compiler (mingw64 v. 4.6.1). Though I'm able to compile the routines from the command line using gfortran '...', .Fortran('foo2') results in an error saying the Fortran

[cc'ing to R-devel] It's moderately obscure to me too, but ... There are two sets of bessel code in the package, one in C++ from Chris Bond and the other in FORTRAN from Netlib (I think). The FORTRAN code is the one that's giving trouble, you might try just removing the FORTRAN code from the src directory and trying again.

Hello everybody Is there a way to output data into a file like the unformatted, direct fortran files? That's the kind that can be opened with: open(30, file='file', format='unformatted', access='direct', rec=1000, convert='big endian') Thank you in advance Kostas Douvis

Hi, Until you get a more definitive answer, I will make an attempt to give some advice. When using an assumed sized array (i.e. REAL*8 array1(*)) you still need to allocate the memory prior to calling the Fortran subroutine, so you would still need to know its maximum length. Arrays created in a Fortran subroutine via the use of the ALLOCATE statements are not simple arrays (in the sense of C

Here are three reasons for converting Fortran code, especially older Fortran code, to C: 1. The C-Fortran interface is not standardized. Various Fortran compilers pass logical and character arguments in various ways. Various Fortran compilers mangle function and common block names in variousl ways. You can avoid that problem by restricting R to using a certain Fortran compiler, but that can

DeaR list, I happily use eigen() to compute the eigenvalues and eigenvectors of a fairly large matrix (200x200, say), but it seems over-killed as its rank is limited to typically 2 or 3. I sort of remember being taught that numerical techniques can find iteratively decreasing eigenvalues and corresponding orthogonal eigenvectors, which would provide a nice alternative (once I have the

Hi, "we can, once we know how to do it, 'drive' R from within FORTRAN" I am not sure I understand what you mean by this ... You can call routines written in Fortran or C from within R - how easy this is depends on the interfaces to those routines. You can call (some) R functionality from C (see for example

That /. shit is indeed VERY annoying :( (FreeBSD dead WTF!!) But if I have to convince a customer why to choose for FreeBSD, I always use Yahoo! as an example. They got some ridiculous traffic and that site is ultra fast. They always buy that :D So for now i dont need an audit > > > ----- Original Message ----- > From: "Devon H. O'Dell" <dodell@sitetronics.com>

Help! I'm running successfully R_0.64.1 under windows95 with bother and thoroughly enjoying using it, but I would prefer to run under UNIX, I downloaded the various files but I'm coming across the following problem. Can anybody suggest anything to help me. Executing ./configure --prefix=/myworkspace/R leads me to R is now configured for mips-sgo-irix6.4 Source directory: .

I browsed through ch.5 of R manual "Writing R extensions". It seems to be written for experienced programmers rathern than for people who occasionally face this problem. A table summarising the main ley points for each supported platform would be very useful. Something like: Supported languages: C, Fortran-77, ...... Windows guidelines: 1. compie Fotran code with (commands) from

My older packages have some Fortran and C routines. The Fortran is ancient and I am started to convert it to Fortran 2018 (thanks ChatGPT). To have a mixture of Fortran and C code in a package I have had a src/init.c file that provides names for routines of the form F77_name, and I called the routines with .Fortran(F77_name, ...) and in NAMESPACE had useDynLib(package name, .registration=TRUE,

okay, i reversed that patch out and solaris 7 still works fine with pam... devon ----- Original Message ----- From: <mouring at etoh.eviladmin.org> To: <devon at admin2.gisnetworks.com> Sent: Thursday, February 22, 2001 10:43 AM Subject: Re: Solaris and Latest snapshot (2001-02-21) (fwd) > > > ---------- Forwarded message ---------- > Date: Wed, 21 Feb 2001 17:54:19