similar to: PKG_CFLAGS/CFLAGS and PKG_CXXFLAGS/CXXFLAGS

Dear R People, in the R FAQ (in the R Programming section) it says ********************************************************************** How can I change compilation flags? =================================== Suppose you have C code file for dynloading into R, but you want to use `R CMD SHLIB' with compilation flags other than the default ones (which were determined when R was built).

Hi. I am writing some code in C that I would like to link into R. My Makevars file is: PKG_CPPFLAGS=-I/usr/local/include PKG_LIBS=-L/usr/local/lib -lgsl PKG_CFLAGS = -Wall -O0 -g -p -pg The source file is core.c,. and I am compiling using R CMD SHLIB core.c The output is gcc -arch x86_64 -O3 -g -p -std=gnu99 -I/Library/Frameworks/ R.framework/Resources/include

On Tue, 8 Feb 2005, Kurt Hornik wrote: > This concerns the packages... > for which current versions of r-devel now report problems with > non-portable compilation flags in Makevars[.in] files: > > Problems in package 'rwt': > Non-portable flags in variable 'PKG_CFLAGS': > -Wall -ansi -pedantic > > These flags are mostly GCC specific and not

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

Hi, Similar questions have come up before on the list and elsewhere but I haven't found a solution yet. winbuilder's install.out shows data.table's .c files compiled with -O3 on Win32 but -O2 on Win64. The same happens on R-Forge. I gather that some packages don't work with -O3 so the default is -O2. I've tried this in data.table's Makevars (entire contents) : ====

Le 27/09/16 ? 13:31, Dirk Eddelbuettel a ?crit : > > On 27 September 2016 at 09:37, Eric Deveaud wrote: > | Hello, > | > | I'm tring to install a Rpackage that holds some C//C++ code > | > | as far as I understood the R library generic compilation mechanism, > | compilation of C//C++ sources is controled > | > | 1) at system level by the ocntentos

Dear People, Over the last few days I've been writing C++ to compile as a shared library (previously I have always used C). Not entirely to my surprise, I am getting errors. Specifically, when I try to load the shared library, I get Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library "/home/faheem/research/thesis/sim/ms/ms.so":

Hi, I'm trying to register my native routines using R_registerRoutines (...). I can compile the code, but the loader cannot resolve the symbol: undefined symbol: _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6 _ $ nm bgx.Rcheck/bgx/libs/bgx.so | grep R_registerRoutines U _Z18R_registerRoutinesP8_DllInfoPK12R_CMethodDefPK15R_CallMethodDefS3_S6

I've been trying to learn about dynamically loading subroutines in R. Ultimately I would like to use this approach to implement some simulations. For the moment though, I've run into a problem compiling c++ code and loading it into R. The 'C/C++' and 'R'code below works fine when compiled and linked with gcc, but gives an error when the library is compiled and linked with

As far as I can see, and even test, R COMPILE CXXFLAGS="..." foo.c works just fine and passes the desired options on to gcc/g++. I have not been able to find a way to do this with R INSTALL foo*.tar.gz, other than by edting $RHOME/etc/Makeconf. While editing Makeconf is probably good enough for most users, it is not something I can do during (automated, unattended) builds of Debian

Hi, what is the correct way to specify a C standard in a package's Makevars file? Building a package with e.g. PKG_CFLAGS = -std=gnu11 does work but R CMD check issues a warning: * checking compilation flags in Makevars ... WARNING Non-portable flags in variable 'PKG_CFLAGS': -std=gnu11 (Same for -std=c11.) Thanks! Regards, Andreas Kersting

>From: "Baptiste Lepilleur" >Date: Tue, 20 Sep 2005 09:29:07 +0200 > >Henrik Bach wrote: >>Hi, >> >>Please have a look on my private Getting started with MinGW: >> >>http://www.geocities.com/henrik_bach_llvm/ > > >Thanks Henrik.The make line was most useful. Though, in my case I also >needed to add a -L so libimagehlp.a would be

On Sep 19, 2007, at 5:41 PM, Devang Patel wrote: > On Sep 19, 2007, at 4:48 PM, Bill Wendling wrote: > > In llvm-backend.cpp : > > 1086 if (GV->getName() != Name) { > 1087 Function *F = TheModule->getFunction(Name); > 1088 assert(F && F->isDeclaration() && "A function turned > into a global?"); > 1089

How can one specify multiple extra flags to R CMD SHLIB? The example in R-exts section 5.5 MAKEFLAGS="CFLAGS=-O3" R CMD SHLIB *.c works for a single flag, but when I try MAKEFLAGS="CFLAGS=-g -O2 -Wall" R CMD SHLIB *.c only the first flag is used and the rest seem to be ignored (version 2.3.1, Mac OS X) -thomas Thomas Lumley Assoc. Professor, Biostatistics

It seems unlink doesn't work with wildcards in 2.5.0. I've tried R-2.5.0 under gnu/linux from source and the Mac binary from att research. Example: > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.*",recursive=T) > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.1",recursive=T)

Dear all, R on Macports relies on GCC 4.3 to build packages. I find that packages with shared objects that use C++ streams crash R if they're compiled using Macports' gcc43, but work fine if compiled in exactly the same way using Apple-supplied GCC 4.2. Has anyone here had the same issue/know what is causing this problem? Thanks, Ernest

Hi This is a question prompted by the mac version of R, but as I see it, it should have broader interest. These days the CRAN Mac binary per default compiles every package for two architectures. First i386 and then ppc. In between the two compilation runs, any object files in pkgname/src is removed. This cleanup is necessary since otherwise Make would not recompile the object files

Hi, R 2.5.0 isn't auto-completing paths properly as it used to. E.g. suppose I have: > dir("CEL/choe") [1] "chipC-rep1.CEL" "chipC-rep2.CEL" "chipC-rep3.CEL" "chipS-rep1.CEL" [5] "chipS-rep2.CEL" "chipS-rep3.CEL" Now if I do: ReadAffy("CEL/choe/ch<tab> # => ReadAffy("CEL/choe/chip

Hi all, I have some C++ code that I call from my package. In my main C++ loop, I check for user interrupts and return to the R shell after ensuring I've deallocated memory appropriately. This works fine when the code is compiled with gcc+openmp and with icc without openmp, but when I compile with icc and use openmp, the entire R session is immediately terminated when I hit ctrl-C. This

Dear all, I have wrapped a C++ function in an R package. I allocate/deallocate memory using C++ 'new' and 'delete'. In order to allow user interrupts without memory leaks I've moved all the delete statements required after an interrupt to a separate C++ function freeMemory(), which is called using on.exit() just before the .C() call. I am concerned about the