Kevin Ushey: (12:10AM on Fri, Jun 07)
I think the key word here is _other_ packages. It's entirely okay to call
your package's own compiled code through the .Call interface (and the code
you write may link to other packages; the obvious example being Rcpp code
you write); however, it is not
Dears,
I am writing a code in Fortran using OpenMP directives.
When compiling the code in gfortran 4.4 does not occur any problem.
When compiling the code in gfortran 4.6, an error message appears.
In other compilers the error does not occur.
A small example.
## Code in Fortran
Dears,
I am writing a code in Fortran using OpenMP directives.
When compiling the code in gfortran 4.4 does not occur any problem.
When compiling the code in gfortran 4.6, an error message appears.
In other compilers the error does not occur.
A small example.
## Code in Fortran
This is not gfortran-help, but note that you are not doing this
correctly. See 'Writing R Extensions' §1.2.1. The linking step needs a
flag too.
Beyond that, you failed to tell us your OS, and in fact there are no
such versions of gfortran (4.6.0 != 4.6). The posting guide does ask
you to
Dears,
I am writing a code in Fortran using OpenMP directives.
When compiling the code in gfortran 4.4 does not occur any problem.
When compiling the code in gfortran 4.6, an error message appears.
In other compilers the error does not occur.
A small example.
## Code in Fortran
Summary:
The directory /usr/local/lib/R/site-library can be used for site-wide
multi-user installations of R.
This is even the default on Debian and Ubuntu (following a suggestion by
Kurt and Fritz a decade ago over beers -- what could be better). However,
R enforces wrong
Hi all,
Dirk Eddelbuettel e...@debian.org writes:
Summary:
The directory /usr/local/lib/R/site-library can be used for site-wide
multi-user installations of R.
This is even the default on Debian and Ubuntu (following a suggestion by
Kurt and Fritz a decade ago over beers --
