search for: pkg_fflags

...m of choice when developing for R, I first got everything done there, using R CMD COMPILE, and R CMD SHLIB. Since g77 complained about the Fortran Codes indentation style, I assumed (after reading g77's manpage) that the Fortran code is given in free-form dialect. Therefore, I added a line PKG_FFLAGS+= -ffree-form to Makevars. Compilation and building went fine and I successfully accessed the routines using dyn.load and .Fortran. My colleague, who wanted this done, runs R under windows. So I learnt how to build a package under windows (readme.packages is a great guide!), and it went all sm...

Hi, I'm searching for a way to override the default CFLAGS/FFLAGS (-g -02 in my case) per package (e.g with "-g" for packages under development). PKG_CFLAGS/PKG_FFLAGS is prepended to the remaining flags, so it can't delete a globally set "-O2" flag. Of course I can edit the global Makeconf file, but I was wondering if there is a possibility to override variables from Makeconf in the Makevars file inside a package tree, without creating a separate...

Dear R Developers, For package seriation I use Fortran code. I recently got a request to add #if defined(__ICC) || defined(__INTEL_COMPILER) USE IFPORT #endif to the code since the Intel Fortran compiler otherwise has problems with rand(). However, to enable the FPP preprocessor I have to either add a compiler flag (-cpp for gFortran) which is possibly not portable or change the

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

Hi, We have several projects in the center done by researchers over years in Fortran, there are copy right issues etc to prevent us from giving away the source codes, but a lot of social scientist are interested to use the program. We tried to use dlls to make plugins (available in our website) in various statistics platforms (SAS, STATA and R) to make it available to general public. We used

...ich includes free-form Fortran 9x code which uses OpenMP should include SHLIB_OPENMP_CFLAGS (or the 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....

...ich includes free-form Fortran 9x code which uses OpenMP should include SHLIB_OPENMP_CFLAGS (or the 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....

...ich includes free-form Fortran 9x code which uses OpenMP should include SHLIB_OPENMP_CFLAGS (or the 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....

...lers (and on macOS, the SDK) used, and this is copied to the output of R CMD check. Where a C++ standard is specified, it is reported. * R CMD check's 'checking compilation flags in Makevars' has been relaxed to accept the use of flags such as -std=f2008 in PKG_FFLAGS. * tools::buildVignettes() has a new argument skip, which is used by R CMD check to skip (and note) vignettes with unavailable \VignetteDepends (PR#18318). * New generic .AtNames() added to enable class-specific completions after @. The formerly internal function findMat...

...lers (and on macOS, the SDK) used, and this is copied to the output of R CMD check. Where a C++ standard is specified, it is reported. * R CMD check's 'checking compilation flags in Makevars' has been relaxed to accept the use of flags such as -std=f2008 in PKG_FFLAGS. * tools::buildVignettes() has a new argument skip, which is used by R CMD check to skip (and note) vignettes with unavailable \VignetteDepends (PR#18318). * New generic .AtNames() added to enable class-specific completions after @. The formerly internal function findMat...