similar to: Makevars PKG_LIBS ignored by SHLIB (PR#9473)

Full_Name: Rick Sayre Version: 2.10.0 OS: linux/windows/os x Submission from: (NULL) (138.72.146.168) Man, it feels ungrateful to report this, but it looks like in the process of having my wish PR#13758 fulfilled, a typo snuck in to the "NEWS" releasenotes: o New as.raw() method for "tclObj" objects (wish of PR#13578). I'm pretty sure that's a typo, and should

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

Dear R-devel, I've written a numerical solver for SOCPs (second order cone programs) in R, and now I want to move most of the solver code into C for speed. I've written combined R/C packages before, but in this case I need to do matrix operations in my C code. As I have never done that before, I'm trying to write some simple examples to make sure I understand the basics. I am stuck

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

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'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

On 28/09/2020 12:44, Andreas Kersting wrote: > 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: for some unstated value of 'work' ... > * checking compilation flags in Makevars ... WARNING > Non-portable flags in variable

Sorry for bothering you I am trying to build the R grpc package on windows: https://github.com/nfultz/grpc against an MSYS2 build of grpc. when running devtools::install() I am getting the following error: C:/msys64/mingw64/include/grpc/impl/codegen/port_platform.h:47:2: error: #error "Please compile grpc with _WIN32_WINNT of at least 0x600 (aka Windows Vista)" #error \ ^ Which,

Dear all, As previously submitted, I wrote an extending pdf device to embed pop up text and web links. (Patches are available at http://pdf2.r-forge.r-project.org/patches) Now, I'm making a library version of the pdf device. However, with my skill, I'm not sure about writing Makevars or configure file for multi platforms. A following line in Makevars works on my mac, -----

Dear R-developers, I am trying to reproduce the autoconf.ac example from R-ext and fail. My autoconf file looks like this [autoconf.ac] # original by Friedrich Leisch, much changed by BDR AC_INIT([SBMLodeSolveR]) dnl Select an optional include path, from a configure option dnl or from an environment variable. AC_ARG_WITH([sbmlode-include],

Howdy, I'm working with some external code written in C++, which I would like to call via dyn.load() and .C() from R. The function prototype looks like: gaRemin(int *, float *, float *, int *, float *, float *, float *, float *, float *) but to call this function from R using .C() I have had to use the mangled version of this

Hello, In the src folder of my R package I have a.cc b.cc f/g/x.cc my Makevars.in has all: $(SHLIB) upon installing only, a.o and b.o is build and the final dll is comprised of a.o and b.o How can I instruct $(SHLIB) to pick up its source files from all subdirectories (or maybe a subset, though here it will be all) in src ? Much thanks Saptarshi

Paul Roebuck wrote: >I have the following contrived code in package format. >On Solaris and Mac OS X, code runs just fine. On Windows, >it crashes the R environment with the "Send Bug Report" >dialog. I tried R 1.8.1 (Win2K) and R 1.9 (WinXP) binaries >with the same result. PCs otherwise appear properly >configured for creating R packages. Anything blatantly >wrong?

Apologies in advance for the long post. I'm currently using a Makefile to build my shared library. Pursuant to the R-exts manual, I'd like to switch to a Makevars file or a configure file if necessary. Having never used these types of make utilities before, I'm a bit lost. My package is quite simple. It only has one source file and one header: excelpoi.cpp excelpoi.h The reason I

So now we have some important context for your original question. I understand why you want "symmetry" but because of the reasons Dirk outlines, I personally think it is a bad idea, ie. I disagree with your statement "anyway I still convinced that if R provides a mechanisn hierachical way of variable overwrite pkg / user/ system it _SHOULD_ be consistent at all levels". The

Hello, I thought that I should try openblas when building a CRAN package containing lots of old (twentieth century) C-code with frequent calls to blas and lapack routines. I have the following options on my Ubuntu 20.04 machine: Selection Path Priority Status ------------------------------------------------------------ * 0

As a package author, it is in my opinion irresponsible to override these system settings (which is why it is also impossible). You have no idea what system it is being deployed on, I mean, you don't even know if the compiler is gcc. If a user wants (say) heavy optimization they will compile R with optimization. (For this reason I also don't think users should modify their ~/.R/Makevars,

[cross-posted from bioc-devel list] Hi all, I have a subtle question related to how R CMD SHLIB handles variables in make child processes. In more detail: I am the maintainer of the 'msa' package which has been in Bioconductor since April 2015. This package integrates three open-source libraries for multiple sequence alignment. This is organized in the following way: in src/, there

Le 27/09/16 ? 16:17, Kasper Daniel Hansen a ?crit : > As a package author, it is in my opinion irresponsible to override these > system settings (which is why it is also impossible). You have no idea > what system it is being deployed on, as the it guy dedicated to install and maintain softs on our cluster I have a reasonable knowledge of the systems I work on. I don't want to

Hello! I have some Fortran code that uses BLAS calls, and would like to compile it into a shared object to call it from R as per the "Writing R Extensions" manual. What needs to go into the "Makevars" file, so that running the R CMD SHLIB will work in Ubuntu? The code compiles properly on the Mac, with the Makevars line PKG_CFLAGS=-Wl,-framework -Wl,vecLib but of course