similar to: DIY Rtools?

Hi, I've been trying to get the python bridge (rpy2) to build for 64-bit R and python. The current stumbling block is that mingw can't use the python27.lib file that comes with CPython and so I need to generate libpython27.a. When I use dlltool from rtools to do that however, I end up with a 32-bit file: >"G:\Rtools\gcc-4.6.3\i686-w64-mingw32\bin\dlltool" -e libpython27.a

Hi, I replaced my Rtools today as posted at http://www.murdoch-sutherland.com/Rtools/Rtools.exe Trying to build R-devel_2007-12-13.tar.gz without modifying MkRules gives the gfortran command not found error below. I am wondering if gfortran.exe is missing from (recent?) Rtools.exe or I am doing something wrong. Thanks to hints at Duncan's site, I worked around the error by adding

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

On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote: >> 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 am planning to

I've seen that many people have had trouble using Rtools for a 64-bit compile of C functions. For some, a quick change in path statement seems to corrects the problem; for others, apparently not. For me? I've been working at path statements and install/uninstall/reinstall of all sorts of things for four hours now with no success. The 32-bit dll loads fine, but I need a 64-bit version. Is

On Thu Jan 9 2014 03:47 Henrik Bengtsson wrote: > This is is an issue that bugged me for a while. I encountered a year > ago (April 2012) when I first tried to build R from source on Windows. > I never figured out what the solution is or if I'm doing something > wrong myself (but I have found a tedious workaround). I'm still on > the same Windows 7 Ultimate machine with

Hi Duncan, On Mon, Mar 9, 2015 at 10:40 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote: >> >> On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at gmail.com> >> wrote: >> > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote: >> >> Hi, >> >> >> >> [This

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

On 30/05/2015 13:14, Duncan Murdoch wrote: > On 29/05/2015 4:16 PM, Sue McDonald wrote: >> My apologies for cross-posting. I found this site, after I had posted on >> stack-overflow. >> >> I need to compile several static libraries (C & Fortran) which will later >> be linked with an R package. Rtools33 directory includes /i686-w64-mingw32 >> directory

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).

Dear All, I'm trying to compile R for Windows 64 bit. I'm following the instructions of R installation and administration guide v2.15.2 (3.1; A.3.1.4; C.2.2) and at the moment I compiled the default version (single threaded, gcc, without external BLAS) ?on my notebook (windows xp 32 bit) Now I'm trying to compile it on Windows servers 64 bit with the next configuration : 1. Windows

Hello all, I'm trying to build R 32bit from source in a Windows 64 machine. I have followed the steps in "R Installation and Adiministration" ( http://cran.r-project.org/doc/manuals/R-admin.html#Getting-the-source-files) or at least I think I did everything described. I am not sure if I have installed the libjpeg, libtiff and libpng files though. I have upzipped them in the

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

hello all, I am trying to compile the R in Win7 and compiles one small part but the script don't move from the 'base' directory to 'stats' I installed the Rtools likee administrator and call the terminal (MS-DOS) like administrator too. if somebody can tell me any tips, I thank in advanced cleber ############################################# File LOG

My apologies for cross-posting. I found this site, after I had posted on stack-overflow. I need to compile several static libraries (C & Fortran) which will later be linked with an R package. Rtools33 directory includes /i686-w64-mingw32 directory which I understand creates 32 bit binaries. Yet, there are other 64 bit directories as well. I have three related questions: 1. Can

Hi Avraham, What a coincidence, I have been following this post of yours: https://www.avrahamadler.com/2013/10/24/an-openblas-based-rblas-for-windows-64-step-by-step/ Looks like this post is slightly older than what you have shared previously. It is strange that you did not get the attachments. I am pasting the contents of the MkRules.local here:

I have just uploaded to CRAN a new version 3.2.0.1948 of Rtools for Windows. This will become visible there in a few hours, and be copied to mirrors thereafter. People who want to build packages that include compiled code can use this to supply the compilers, etc., that are necessary for the build. It also includes some extra materials for people who want to build R itself. This version

On Tue, Mar 10, 2015 at 4:07 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 09/03/2015 11:02 PM, Hsiu-Khuern Tang wrote: >> Hi Duncan, >> >> On Mon, Mar 9, 2015 at 10:40 AM, Duncan Murdoch >> <murdoch.duncan at gmail.com> wrote: >>> On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote: >>>> >>>> On Mon, Mar 9, 2015 at

Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the

On Wed, Mar 11, 2015 at 1:23 PM, Hsiu-Khuern Tang <tangoh at gmail.com> wrote: > On Tue, Mar 10, 2015 at 10:47 PM, Avraham Adler <avraham.adler at gmail.com> wrote: >> On Wed, Mar 11, 2015 at 1:40 AM, Hsiu-Khuern Tang <tangoh at gmail.com> wrote: >>> On Tue, Mar 10, 2015 at 8:54 PM, Avraham Adler <avraham.adler at gmail.com> wrote: >>>>