Yay! I got it to work! I used the ~/.R/Makevars, and all is well.
Thanks again,
Erin
Erin Hodgess, PhD
mailto: erinm.hodg...@gmail.com
On Mon, Aug 27, 2018 at 2:29 PM Kevin Ushey wrote:
> Hi Erin,
>
> The R extensions manual should be helpful here -- in particular, see the
> sections on the
Thank you, Kevin!
I put together the Makevars file:
PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS)
FC=c:/progra~1/PGICE/win64/18.4/bin/pgf90
SAFE_FFLAGS="-Lc:/progra~1/PGICE/win64/18.4/lib/pgf90.dll
-Lc:/progra~1/PGICE/win64/18.4/lib/pgc14.dll"
rmpiFort.obj: rmpiFort.f90
$(FC) $(SAFE_FFLAGS) -M
Hi Erin,
The R extensions manual should be helpful here -- in particular, see the
sections on the 'src/Makevars' file and configuration of the Fortran
compiler:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-Makevars
In particular, in your 'src/Makevars' file, you'll likely w
Hello!
I'm building a package on Windows 10 which uses the PGI Fortran compiler.
I have a Makefile set up in the src directory, and when I run "make all",
the subroutines compile beautifully.
Now I want to create my package. When I run R CMD check, naturally,
gfortran is called. Is there a way