similar to: Graceful exit from fortran.

Full_Name: G?ran Brostr?m Version: R-2.1.1, 2.2.0 OS: Debian unstable Submission from: (NULL) (213.65.9.59) Some BLAS routines call xerbla for error messages, which results in a message like "LAPACK routine DGER gave error code -9". Suggested solution: In void F77_NAME(xerbla)(char *srname, int *info) { /* srname is not null-terminated. It should be 6 characters. */ char

I am making my first attempts at using some Fortran code with R, and so far it's going OK. To print from my Fortran programs, it seems I need subroutines dblepr, realpr and intpr. From the excellent "Writing R Extensions" document: "Three subroutines are provided to ease the output of information from FORTRAN code. subroutine dblepr(label, nchar, data, ndata)

Hi I've built a dll using Fortran code and can call it by either R or Fortran. Calling by the former gives me the wrong answer and the later gives the correct answer. From what I've read, it looks like I should use the subroutines DBLEPR, INTPR and REALPR to get values to show up in R which I hope will allow me to find the error. I've downloaded the R-2.12.0.tar.gz but have

Has anyone ever successfully used Fortran character strings with R? ?Foreign says R C Fortran integer int * integer .... character char ** [compiler dependent] Character strings are passed as C arrays of character strings to Fortran: the first string may be usable if its length is passed

Hi, I have tried to pinpoint potential problems which could lead to the LAPACK issues that are currently seen in R. I built the current R trunk using AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto --enable-BLAS-shlib=no --without-recommended-packages and used this to find problem areas. There are quite a few warnings that were flagged, due to mismatches in function

Dear list, I?m trying to register Fortran routines in randtoolbox (in srt/init.c file), see https://r-forge.r-project.org/scm/viewvc.php/pkg/randtoolbox/src/init.c?view=markup&root=rmetrics. Reading https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Registering-native-routines and looking at what is done in stats package, I first thought that the following code will do the job:

Hi, everyone. This may be properly a fortran question rather than an R question. I'm trying to add a few print statements to otherwise working fortran code in one of the libraries so I can see what's going on in the code. I have no problem doing so on an SGI machine, but under LinuxPPC I've run into a problem. The code compiles and creates a shared object (.so), but when I issue

I'm trying to figure out why the presence of a Fortran call affects the result of a floating-point operation. I have C functions void test1(int *n, double *f){ int outC; double c0; c0 = (double) *n * *f; outC = floor(c0); printf("when f computed by R, C says %d by itself\n",outC); } void test2(int *n, double *f){ extern int F77_NAME(ifloor)(double *); int

Hi I've built a dll using Fortran code and can call it by either R or Fortran. Calling by the former gives me the wrong answer and the later gives the correct answer. >From what I've read, it looks like I should use the subroutines DBLEPR, INTPR and REALPR to print to the R console rather than using Fortran standard I/O and that if I use the command R CMD SHLIB source.f that these

Hello, I am trying to call the BLAS Level1 function zdotc from R via a .C call like this: #include "R.h" #include "R_ext/BLAS.h" void testzdotc() { Rcomplex zx[3], zy[3], ret_val; zx[0].r = 1.0; zx[0].i = 0.0; zx[1].r = 2.0; zx[0].i = 0.0; zx[2].r = 3.0; zx[0].i = 0.0; zy[0].r = 1.0; zy[0].i = 0.0; zy[1].r = 2.0; zy[0].i = 0.0; zy[2].r = 3.0;

Hello All, In some package I use a c-routine which calls a fortran routine which expects a char-string as input. As per the writing R-extensions manual, the Fortran routine is declared in C as: void F77_NAME (setoptions) (char **option); and then it is calles as follows: char **option; option = new char*[1]; option[0] = new char[256]; option[0] = strcpy(option[0],"Iteration

Hi all, im triyng to implement a bayesian model with R and c++. I have a strange problem. I can't reproduce the error with a small script and then i post the original one. The problem is after the line for(MCMC_iter2=0;MCMC_iter2<thin;MCMC_iter2++) For the first 34 iterations all work fine, after, all the simulations of mu_acc_P return an "nan". If i delete the line

Dear R-devel, I am trying to use Fortran DGESV subroutine into C. Here it is the relevant part of the C file I am currently writing #include<stdio.h> #include<R.h> #include<Rmath.h> #include<math.h> void F77_NAME(DGESV)( int*, int*, double*, int*, int*, double*, int*, int*); void solve( int *p, double *A, double *Ainv) { ... F77_CALL(DGESV)(p, p, Ain, p, ipiv,

Hello, I submitted a package which used Fortran functions isnan and lgamma. However, I was told that: isnan and lgamma are not Fortran 95 functions. I was asked to write 'cross-platform portable code' and so should not be writing GNU extensions to Fortran. See http://cran.r-project.org/web/checks/check_results_mpath.html, which will shortly show installation failures under Solaris. I

I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri) ? Thank you. Kevin

Hello, I am trying to install R packages under linux, some of the packages can not be installed and I got the following error, could anybody give me suggestion on where the problem is and how to fix it? Thanks-e > .libPaths() [1] "/usr/lib64/R/library" [2] "/usr/share/R/library" [3]

Hi, I am searching for a way to solve the following problem: I want to use an external function, defined in a dyn.load()ed shared object, in another dyn.load()ed shared object. Currently I have to take the sources (Fortran) from one libraries src/ directory and copy them into the src/ dir of the other library, resulting in two copies of this function. This is bad for maintanance and maybe also

On Wed, 4 Aug 1999, Peter Ho wrote: > I have been browsing in the contributed packages webpage and found that > there is an R port for MClust. Is there a way I can use it using the > windows port of R 0.64.2? I could not find a windows port of MClust. Simple reason: I was not able to compile it successfully under Windows. I did make it compile after a lot of effort, but it crashed R on

Hello there I'm writing some c-code to solve a numerically tough problem for me in R. Looking in Lapack.h, i find the following line F77_NAME(dgesvx)(const int* fact, const char* trans, const int* n, and I believe that "fact" should've been char instead of int, i.e. F77_NAME(dgesvx)(const char* fact, const char* trans, const int* n, My reasoning: In the R-source:

I'm developing some software and running into compiling warning: conditionals.c:104: warning: passing argument 4 of 'dger_' discards qualifiers from pointer target type conditionals.c:104: warning: passing argument 6 of 'dger_' discards qualifiers from pointer target type the netlib documentation states that the arguments x and y should be unchanged on exit. Should should