[R-sig-hpc] Makevars.in - changing compiler
Davor Cubranic
cubranic at stat.ubc.ca
Fri Dec 10 18:35:05 CET 2010
You *can* modify the package compiler -- for example gputools switches
to using nvcc CUDA compiler. But I'm pretty sure you'll need to use a
custom Makefile.
Davor
On December 8, 2010 06:17:41 am George Ostrouchov wrote:
> Hi Dirk,
>
> Here is some more detail that I should have included earlier. I am
> extending the ncdf4 package to include parallel I/O (already
> available in NetCDF4) so it needs Open MPI includes and libs. Just
> swapping the compiler to mpicc will take care of things. ncdf4 uses
> autoconf and the Makevars.in mechanism. Can the package compiler be
> specified this way?
>
> Thanks,
> George
>
> On 12/7/10 11:52 PM, Dirk Eddelbuettel wrote:
> > On 7 December 2010 at 23:44, George Ostrouchov wrote:
> > | Is it possible to set a package compiler via Makevars.in? I need
> > | to substitute mpicc (an Open MPI wrapper compiler). My attempts
> > | just setting CC=mpicc in Makevars.in have failed.
> >
> > For an R package?
> >
> > | Is Makevars just "included before the default `Makefile'" as it
> > | states in the "Writing R Extensions" manual or is there more to
> > | it?
> >
> > Here is what the current Rmpi has in src/Makefile.in:
> > # -*- Makefile -*- vim : ft = make
> >
> > PKG_CPPFLAGS = @DEFS@ @PKG_CPPFLAGS@
> > PKG_CFLAGS = $(ARCHCFLAGS)
> > PKG_LIBS = @PKG_LIBS@ $(ARCHLIB)
> >
> > As you can see, it only sets arguments to the compiler, not the
> > compiler itself.
> >
> > Rmpi is a pretty good package to study as Hao as been diligently
> > working at it for many years, and has it working for a great
> > number of system and compiler choices.
> >
> > Did that help? If not please rephrase the question.
> >
> > Cheers, Dirk
More information about the R-sig-hpc
mailing list