similar to: Rtools and MinGW

Hi all, I'm trying to set up the Windows Rtools toolset for building packages with compiled code. I installed for Windows R-3.4.3 from CRAN and installed Rtools-3.4 in a custom location M:\R\R-3.4.3 and M:\R\Rtools-3.4 Following the instructions, in shell, I set Path=M:\R\Rtools-3.4\bin;M:\R\Rtools-3.4\gcc-4.6.3\bin;M:\R\R-3.4.3\bin;... (the ... are other paths irrelevant for R/Rtools).

Hi, Moving to a new computer (Windows 7) but for reasons of reproduceability I would seriously like to also install my present R 2.8.1 along with all extension packages on that machine as well (that is besides R 2.14.1). What's the best way of doing so? My idea is: Get the setup for 2.8.1 and install it; during install neither select 'save version number in registry' nor

De: Rubén Roa Enviado el: jueves, 17 de noviembre de 2011 9:53 Para: 'Users@admb-project.org' Asunto: Reporting a conflict between ADMB and Rtools on Windows systems Hi, I have to work under Windows, it's a company policy. I've just found that there is a conflict between tools used to build R packages (Rtools) and ADMB due to the need to put Rtools compiler's

Hi, I'm trying to build the termstrc 1.1 package from its source on R 2.7.2 on Windows XP. However instead of building the package it just zips the entire source into a .tar.gz file. This is the first time I'm trying to build an R package from source. I installed the R toolset for Windows and set RTools as well as Perl & MinGW directories in the path. Anybody tried this out? Any file

I've just discovered that Rtools (on Windows) contains Python interpreter(s). I'm assuming that Python is required to build R packages, on all operating systems. I think this is a mistake. Also, by my count, Rtools contains six Python interpreters. I've miscounted, I hope... [[alternative HTML version deleted]]

Hi, [This is a follow-up to the "New version of Rtools for Windows" thread in January, but I just subscribed and don't know how to reply to an old thread -- my apologies.] I was able to use the nuwen distro to build a gcc 4.9.2 toolchain and use it to build the latest R-patched with it. Below are some notes about what I did; I hope they will be useful for keeping Rtools

I have some C code (using an old Borland compiler) that calls a DLL that I'd like to get working from Windows and R (so I can read ABF files -- Axon Binary Files -- directly in R). I thought a good first approach would be able to build R in Windows, so that's what I'm trying to do. [I've done test builds of R under Linux before, and that seemed fairly simple.] I've

On Tue, Feb 13, 2018 at 2:20 AM, Jeroen Ooms <jeroenooms at gmail.com> wrote: > Thanks for your question. Your logs show that 'gcc' is not found. As > of R 3.3 you need to set the path to the compiler using the BINPREF > variable. This is because we ship two separate versions of gcc, one > targeting win32 and one targeting win64. I am not sure what your > rtools

I started working on some R bindings for mongo-c-driver [1]. The C library compiles fine on Ubuntu Trusty (gcc 4.8.2) and osx (clang), however on my windows machine (gcc 4.6.3 from Rtools 3.1) it fails with: 'INIT_ONCE_STATIC_INIT' undeclared. Google suggests that this might be a problem in older versions of mingw-w64. So I grabbed a copy of mingw-w64 version 4.8.3 and indeed, here the

Never mind. Found the solution: the package coded the rtools path in Makevars.win. So I was able to compile (but have another problem though). But not sure if there is an environment name for rtools, maybe RTOOLS_HOME ... Thanks. ----- Forwarded Message ---- From: Andy Zhu <andyzhu35@yahoo.com> Cc: r-help@r-project.org Sent: Mon, December 20, 2010 11:33:31 PM Subject: [R] R CMD

Dear R-devel community, I'm exploring (experimentally) the integration of the Rust toolchain into Rtools, to enable smoother development and shipping of Rust-based R packages on Windows. I've written a detailed blog post documenting the process, technical rationale and what?s next: https://medium.com/@sunwjie/integrating-the-rust-toolchain-into-rtools-e4c7df40cb82. Currently, Rust is

>> I am trying to compile rseries from Whit Armstrong and a colleague of mine found a problem with using GCC4 I get the following error when compiling rseries g++-sjlj -Ic:/R/include -O2 -Wall -c Rutils.cpp -o Rutils.o Rutils.cpp: In function 'double* getColPointer(SEXPREC*, int)': Rutils.cpp:406: warning: deprecated conversion from string constant to 'char*'

I've been getting pqR to work on windows systems, and in the process have discovered various problems with R core versions of R and with Rtools. One is with the implementation of OpenMP in 64-bit Rtools. This problem is in Rtools215 and Rtools33, and presumably all the ones in between. You can see the problem with the following test program: #include <stdio.h> #include <omp.h>

Hi, I am trying to install a package (PortfolioAnalytics) of R 2.15.2 on Win 7. I have tried the following instructions on : http://stackoverflow.com/questions/11105131/cannot-install-r-forge-package-using-install-packages I used svn checkout svn://svn.r-forge.r-project.org/svnroot/returnanalytics/ to get the package and then copy it to my Win 7. Then, on Win 7 I run: >

Hello, I have a problem with the checking and building of R packages that contain C or FORTRAN code. I have implemented R 2.3.1 (2006-06-01) and the corresponding toolset under Windows XP and Windows 2000. The MinGW compiler components are (exactly as recommended for R 2.3.1) gcc-core-3.4.5-20051220-1.tar.gz gcc-g++-3.4.5-20051220-1.tar.gz gcc-g77-3.4.5-20051220-1.tar.gz

It appears that Mingw gcc included in RTools is missing a dependent library. If I compile a program with '-lgomp' switch (for OpenMP support), I get a errors about undefined references to functions like '_imp__pthread_mutex_destroy'. Adding the '-static' switch, I get the following error: c:/rtools/mingw/bin/../lib/gcc/mingw32/4.5.0/../../../../mingw32/bin/ld.exe:

Congratulations on figuring out how to extend the build of the Rtools installer to add more programs there - it is always good to have a confirmation such things are clear enough from the available documentation and sources. You can see that e.g. QPDF is added this way, but adding a toolchain requires a different approach (more below). What may not have been clear enough - please keep in mind

I can confirm the behaviour that you report.? Usually I put Rtools in c:\programs\Rtools and modify the path accordingly. Recently (don't recall for how long) I have encountered the same problems as you have and I have resorted to moving Rtools to c:\Rtools I have no idea as how to proceed; perhaps it could be worth trying an older version of Rtools (though that may cause other problems).

Yep - simpleITK is available at github.com/SimpleITK/SimpleITK. There's also github.com/SimpleITK/SimpleITKRInstaller - a devtools based installer for mac and linux. CMake has a range of build environments. I experimented with MSYS2 and mingw makefiles, but had trouble with incompatibilities in the path required by CMake and those options - from memory the sh in RTools/bin caused problems.

On Tue, Feb 13, 2018 at 7:45 AM, Peter Langfelder <peter.langfelder at gmail.com> wrote: > Hi all, > > I'm trying to set up the Windows Rtools toolset for building packages > with compiled code. I installed for Windows R-3.4.3 from CRAN and > installed Rtools-3.4 in a custom location M:\R\R-3.4.3 and > M:\R\Rtools-3.4 > > Following the instructions, in shell, I