similar to: R_MAKEVARS_SITE for multiple archs

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

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 RHOME/etc/Makeconf 2) at user level by the content of ~/.R/Makevars 3) at package level by the content of src/Makevars Problem I have is that src/Makevars is ignored see

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,

One other solution that's only a little crazy: you could have a R function within your package that generates the appropriate (portable) Makevars, and within the package `configure` script call that function. For example" R --vanilla --slave -e "source('R/makevars.R'); makevars()" And that 'makevars()' function could generate portable

Dirk Eddelbuettel <edd at debian.org> schreef: > On 13 May 2015 at 17:27, Jan van der Laan wrote: > | > | I have some cpp-files from another library (boost) in a subdirectory > | in my src directory (src/boost_src). I include these using the > | following two lines in my Makevars: > | > | SOURCES = $(wildcard *.cpp boost_src/*.cpp) > | OBJECTS = $(SOURCES:.cpp=.o)

On May 13, 2015, at 2:28 PM, Henrik Bengtsson <henrik.bengtsson at ucsf.edu> wrote: > While at it: 'Makevars' is an R invention (i.e. documentation of it > is only available through the R docs), correct? /Henrik > Well, it's just a Makefile fragment that gets included along with the rest of the Makefiles, so for all practical purposes it's just a Makefile which

Dear R developers, I am seeking advice on some $subject matter. My package will have an update soon, that is not backward compatible with the current version. It will likely break much of the existing code. Many (~50) packages depend on 'igraph' and they, too, will most probably break with the new version. My intended solution is, that I create a snapshot of the current package, under

The build system rolled up R-3.0.1.tar.gz (codename "Good Sport") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-3/R-3.0.1.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team Peter Dalgaard These

Hi, I asked some days ago how to guess the o.s. the machine is running. I found that it is stored in a variable called R_PLATFORM. Now I need a full list of all the values this variable can have because I need to set an option depending on the endianness of the platform in which we are compiling the package. Anyone can help me? Thanks, Virgilio Gómez Rubio Dpto. Estadística e

A command R CMD build <pkg> that fails, e.g., because of C code compilation errors, leaves a directory %TMPDIR%/Rinst.xxx containing the file R.css. Although R CMD INSTALL --build cleans up after itself, build does not. A fix is below. Also, build.in references Rcmd.exe, which I thought was no longer necessary? Index: build.in

I am using the code below to output some network measures: central_social <- data.frame(V(s641_social)$name, indegree_social, outdegree_social, incloseness_social, outcloseness_social, betweenness_social, eigen_social) and I get the following error: Error in Re(z) : non-numeric argument to function I know this has to do with V but I cannot figure out what is wrong. s641-social is a graph

Patch extracts MSB/LSB info from /bin/file output and passes it as separate parameret from elf_arch. Then it is sent to impl_file_architecture and checked/ Modified magic_for_file to handle regex changes. Now with tests for file_architecture. Fixes: RHBZ#1211996 Maros Zatko (2): inspector: recognize ppc64 and ppc64le archs (RHBZ#1211996) tests: ppc64 and ppc64le for file_architecture

hi, as of the moment, llvm-objdump fails on every archs, except x86, arm, aarch64, mips and some other "minor" archs. some notable ones are PPC, Sparc, .... this is due to the lack of support for disasm component of those archs in MC. any plan, roadmap, or anybody is thinking about fixing this? thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am just trying to adjust one of my packages so the C code builds in Windows. This is code that has been around for a long time, and I'm am only a casual reader of C, so it has had the "if it is not broken don't touch it" approach for many years. The section 1.2.1 "Using Makevars" of "Writing R extensions" starts: "Sometimes writing your own

I would like to get the name of the user form the system. Is it possible ? Something like >system.user() returning something like [1] "etber12" Thanks, Etienne [[alternative HTML version deleted]]

On 18 Jan 2014, at 14:31, Axel Urbiz <axel.urbiz at gmail.com> wrote: > Hi All, > > > I'm planning to submit my first package to R, and although I read all the > documentation, I'm not very clear on the following 2 items, from which I'd > appreciate your guidance: > > > 1)I understand it is suggested to use the R dev version to build the >

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

I'm just curious. Why making "if" generic is even more dangerous? Best, Da On Sat, Mar 4, 2017 at 1:22 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > `!` is a generic, `if` is not. You can define an `if` that is generic, > but this might be even more dangerous.... > > ? `if` <- function(a, b, c) UseMethod("if") > ? `if.default` <-

Running the basic (--disable-thorough-tests) test suite, I get these failures round-trip test (rt-1-24-111.raw) encode... Segmentation fault (core dumped) ERROR FAIL: ./test_flac.sh fsd24-01 (--channels=1 --bps=24 -0 -l 16 --lax -m -e -p): encode...ERROR during encode of fsd24-01 FAIL: ./test_streams.sh on alpha and amd64. By contrast, i386 is fine. (All OpenBSD/4.2.) Could be a generic LP64

Hi all, I am running R 2.6.2 in Windows XP with Rtools 2.7 and am trying to compile a shared library in Windows with customized level of optimization. Specifically, I would like to have "-O3 -funroll-loops" as flags when I run "R CMD SHLIB ***.cc" to speed the program for my simulations. I have read through the documentation and have tried adding the line PKG_CXXFLAGS =