On 14 September 2017 at 15:56, Stefan McKinnon Høj-Edwards wrote:
| Oh. I was under the impression the risk of interference was only for stdout
| and stderr.
|
| I suspect the affected Fortran subroutines should be re-written in R or C.
| Is writing to files with Rcpp affected by the interference
Oh. I was under the impression the risk of interference was only for stdout
and stderr.
I suspect the affected Fortran subroutines should be re-written in R or C.
Is writing to files with Rcpp affected by the interference?
Or would it be feasible to have the Fortran subroutine call a C subroutine
On 14/09/2017 9:20 AM, Stefan McKinnon Høj-Edwards wrote:
Dear all,
I am in the process of preparing a R-package that uses Fortran subroutines,
and upon R CMD check (both local and on win-builder), I receive the
following Note:
File 'Siccuracy/libs/i386/Siccuracy.dll':
Found '_gfortran_st_wr
