search for: pkg_fcflag

...a simple hello world but I'm not able to set the number of threads. I found this old email chain <http://r.789695.n4.nabble.com/Set-the-number-of-threads-using-openmp-with-C-td2284685.html> and I tried to set my compile instructions accordingly but i had no luck. *This is my makevars:* PKG_FCFLAGS="-fno-stack-protector" F90FLAGS = "-fopenmp" LDFLAGS = "-fopenmp" *This is my Fortran module:* module hello_openmp use omp_lib implicit none contains subroutine hello(ncores) bind(C, name="hello_") use, intrinsic...

...M Ignacio Martinez <ignacio82 at gmail.com> wrote: > > > I was able to make some progress by using this > <https://github.com/bert9bert/ParallelForest/blob/master/src/Makevars> as > a reference. Now: > > *This is my makevars:* > ##### Compiler flags ##### > PKG_FCFLAGS = $(SHLIB_OPENMP_FFLAGS) > PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) > > ##### Phony target for R's build system to invoke ##### > all: $(SHLIB) > > ##### Clean target ##### > clean: > rm -f *.o *.mod > > And when I run my hello world function all the threads are used...

I was able to make some progress by using this <https://github.com/bert9bert/ParallelForest/blob/master/src/Makevars> as a reference. Now: *This is my makevars:* ##### Compiler flags ##### PKG_FCFLAGS = $(SHLIB_OPENMP_FFLAGS) PKG_LIBS = $(SHLIB_OPENMP_CFLAGS) ##### Phony target for R's build system to invoke ##### all: $(SHLIB) ##### Clean target ##### clean: rm -f *.o *.mod And when I run my hello world function all the threads are used regardless of what i specify: > hello(ncor...

...d that if I use the command R CMD SHLIB source.f that these subroutines will automatically be found (Please correct me if I'm wrong about any of this). The problem is that I have to specify the gfortran compiler option -fno-range-check in order for my code to compile. I've tried setting PKG_FCFLAGS=-fno-range-check in a file named Makevars under the same directory as my Fortran files but this doesn't seem to be the right place because R CMD SHLIB still produces error messages related to integer overflow (the same error as when I run gfortran -c MRPP.f90 as opposed to gfortran -c MRPP...

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

Dear, When trying to use directive OpenMP in my code, I observed that the directive ones were being considered as commentaries. Compiling with command R CMD SHLIB xxx.f95 - fopenmp and calling the function in the R verified that threads was not being considered. I was to observe the options of the compiler R CMD SHLIB --help Usage: R CMD SHLIB [options] files | linker options Build a shared

Hi, I created a R library that uses a Fortran module. Everything works like a charm on linux. Now I'm trying to make it work on Windows. I cloned my git repository <https://github.com/ignacio82/MyPi> on a windows computer, and when I press the build and reload button on Rstudio I get these errors: ==> Rcmd.exe INSTALL --no-multiarch --with-keep.source MyPi * installing to library

I am reading the manual sections illustrating how to call a Fortran subroutine from R. I feel uneasy at the explicit statement about ".Fortran" interface working with Fortran 77. I would like to call a Fortran-90 subroutine from my R script. Is that supported at all ? Thank you, Maura tutti i telefonini TIM! [[alternative HTML version deleted]]

You should be able to set PKG_FCFLAGS="-fno-stack-protector" when compiling to ensure that the stack protector is not used. (Trying that out on a Windows VM, with a simple `R CMD build` + `R CMD INSTALL`, compilation of your package succeeded but linking failed saying the DLL 'Fpi' was not found; I imagine that'...

...he CXXFLAGS version if they also include C++ code) in PKG_LIBS rather than SHLIB_OPENMP_FCFLAGS - fortunately on almost all current platforms they are the same flag. * Macro PKG_FFLAGS will be used for the compilation of both fixed-form and free-form Fortran code unless PKG_FCFLAGS is also set (in src/Makevars or src/Makevars.win). * The make macro F_VISIBILITY is now preferred for both fixed-form and free-form Fortran, for use in src/Makevars and similar. * R CMD INSTALL gains a new option --strip which (where supported) strips installed shared o...

...he CXXFLAGS version if they also include C++ code) in PKG_LIBS rather than SHLIB_OPENMP_FCFLAGS - fortunately on almost all current platforms they are the same flag. * Macro PKG_FFLAGS will be used for the compilation of both fixed-form and free-form Fortran code unless PKG_FCFLAGS is also set (in src/Makevars or src/Makevars.win). * The make macro F_VISIBILITY is now preferred for both fixed-form and free-form Fortran, for use in src/Makevars and similar. * R CMD INSTALL gains a new option --strip which (where supported) strips installed shared o...

...he CXXFLAGS version if they also include C++ code) in PKG_LIBS rather than SHLIB_OPENMP_FCFLAGS - fortunately on almost all current platforms they are the same flag. * Macro PKG_FFLAGS will be used for the compilation of both fixed-form and free-form Fortran code unless PKG_FCFLAGS is also set (in src/Makevars or src/Makevars.win). * The make macro F_VISIBILITY is now preferred for both fixed-form and free-form Fortran, for use in src/Makevars and similar. * R CMD INSTALL gains a new option --strip which (where supported) strips installed shared o...